named timeout when trying to resolve a certain (definitely exisiting) hostname on the internet
Mark_Andrews at isc.org
Mark_Andrews at isc.org
Tue Nov 6 22:09:43 UTC 2001
This is a well known limitation of BIND 4 and BIND 8 (<
8.3) where named doesn't chase down chains of nameservers.
To locate axa.de you have to find the addresses for
dns01.pironet-ndh.com, dns02.pironet-ndh.com and
dns03.pironet-ndh.com. Now to find the addresses for these
servers you have to find the addresses for dns.ndh.net and
dns2.ndh.net. You also have to know the addresses for all
the parents.
This configuration is known not to work with the above
servers (when starting from a empty cache). I've yet to
understand why anyone would want to configure the DNS like
this. All it does is introduce extra failure points and
increase the amount of lookups (and hence time) it takes
to resolve a address. ISP should know better. Configuring
the nameservers like this is a dis-service for their
customers. This is not the worst case, I've seen chains
5 hops long before you start going back up the heirarchy.
If nameservers served the zone they live in (which used to
be the case for years) then you don't have this sort of
problem.
Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
More information about the bind-users
mailing list