In
<Pine(_dot_)LNX(_dot_)4(_dot_)44(_dot_)0412292011200(_dot_)2279-100000(_at_)sokol(_dot_)elan(_dot_)net>
"william(at)elan.net" <william(_at_)elan(_dot_)net> writes:
On Wed, 29 Dec 2004, wayne wrote:
In
<Pine(_dot_)LNX(_dot_)4(_dot_)44(_dot_)0412291338040(_dot_)2279-100000(_at_)sokol(_dot_)elan(_dot_)net>
"william(at)elan.net" <william(_at_)elan(_dot_)net> writes:
DNS administrators typically do not see one record applying for everything
else in that zone and for all subdomains. It never happened before and they
will not realize it until somebody tells them. Some will consider it
usefull
and some will not but I think majority who add the record will not know
about its "*" applicability. That is why I said that one of the best ways
to use specify "*"-like subdomain "*spf*" or possibly just "**" (this
being more if possibly other applications follow spf on zonecut tests).
Well, things like the SOA record and the NS records apply to all
subdomains that are within the same zone.
NS and SOA are records have special meaning when they are on the root of
zone - SOA is not used at all except at the zone boundary and NS have
slightly different meaning when not at zone boundary. And in case of NS
and SOA its the name server that provides these records as part of the
answer not application that queries for them (unless specifically directed
to do so).
SOA records *are* used in other cases. For example, they provide the
nTTL time for cases where a domain is not found.
Yes, NS records have slightly different functions when not at the top
of the zone. The same is true for SPF records when the zone cut
portion of the spec is implemented.
-wayne