Different behaviour for different TLDs?

Konrad Lienhard konrad.lienhard at remove_darki.ch
Thu Oct 9 09:15:12 UTC 2003


> Well technically it's not considered "caching" but yes, each TLD zone
> contains a copy of the A record(s) for every delegated nameserver which
> happens to also have its name in the same TLD. If a .com subzone is
> delegated to one or more nameservers in the .com domain, then there must
> be corresponding A records in the .com zone itself (otherwise resolution
> would get in this chicken-and-egg situation of not being able to resolve
> anything in a zone because it cannot resolve the names of the
> nameservers for the zone, and so on and so on and so on).
>
> For gTLDs like .com, one would usually get these "glue" records updated
> through one's registrar.

What I don't understand is:

I created a subdomain with a seperate dns server responsible for it
(nameserver.subdomain.domain.com)
when I do a whois for "domain.com" I get the the 2 nameservers for the
domain.
If I do a whois for the "subdomain.domain.com" I get nothing
(which is expected as I only delegate the subdomain from my domainservers).
However if I directly
ask a .com TLD Server for "nameserver.subdomain.domain.com" I get directly
an answer but with
the OLD ip not the new one. I neither know why the TLD have this entry
chached nor why they do not
update this entry. Why did they cache this entry in the first place? To my
understanding they should
not cache it because it's my nameservers which are delegating my subdomains
or am I wrong?
I did similar configurations already for .ch domains. There its no problem
at all because the TLD for .ch are just answering with
the dnsserver responsible for "nameserver.subdomain.domain.ch".

Thanks in advance

Konrad




More information about the bind-users mailing list