Contacting ROOT nameservers
Mark.Andrews at nominum.com
Mark.Andrews at nominum.com
Fri Feb 11 02:33:53 UTC 2000
If things were stuck it was because your client asked for
information that was not local. See resolv.conf and the
search directive. Killing the hints just caused named to
return SERVFAIL faster.
I suspect that you have a mixture of pre and post RFC 1535
aware resolvers.
Mark
> Hi Folks
>
> A few days ago my primary DNS (Bind 8.2.2 P5 on RedHat 6.1) was unable
> to reach the root nameservers due to phisical connectivity problems;
> after a restart named was unable to resolve even my internal names
> because apparently it was stuck just searching the unreachable root
> servers over and over and over again.
> querying the nameserver with nslookup result in a timeout message in
> 90% of the times while the remaining 10% were 5% good answers and 5%
> unknown answers (I guess that the good ones came from the cache).
>
> When I restarted named excluding the hint zone from named.conf the
> internal resolution worked fine.
>
> Now I'm wondering if there is a way to force Bind (named) to ignore
> ROOT nameservers after a certain number of failure
>
> thanks to all of you for your time
>
> regards
> Mario
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>
>
--
Mark Andrews, Nominum Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at nominum.com
More information about the bind-users
mailing list