home.com didn't resolve for 29+ hrs??
barmar at genuity.net
Thu Oct 25 21:36:45 UTC 2001
In article <9r9vqp$2bf at pub3.rc.vix.com>,
baywood <baywood at nopambigfoot.com> wrote:
>In article <9r9bbk$sh0 at pub3.rc.vix.com>, "pelln"
><pelln at icke-reklam.ipsec.nu.invalid> wrote:
>> baywood <baywood at bigfoot.com> wrote:
>>> This isn't the first time I've had a problem w/ @home resolving. I
>>> guess I'm hoping someone can confirm I'm not nuts or doing something
>>> weird/wrong. Why couldn't the root DNSs answer home.com queries? I
>> You have not asked a root-nameserver, 184.108.40.206 is
>That was the
>$ dig @220.127.116.11 home.com
>query. Instead of using the root servers (default) I specified an
Since when are the root servers the default? The default is whatever you
have in your /etc/resolv.conf. These should be servers that have recursion
BTW, if any higher-level servers were to blame, it's probably the GTLD
servers, *not* the root servers.
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
More information about the bind-users