Not able to resolve external names

[John Ross]

How does bind 4.9.7 go about contacting .com, .net, etc?  What I mean is,
when you try to resolve something outside of your local domain, what process
happens (or in this case is not happening).  I am assuming that it tries to
contact one of the root name servers, but which one?  Is it random, or do
you know with some certainty which one it goes to?

This is really weird.  In nslookup if you do a "server
some-root-name-server" then it can resolve stuff, but if it points at
itself, the queries just timeout.

John

-- 
John Ross 
Systems Management Integration Professional - Adv
Data Management Solutions 
IBM, Inc. 
16011 College Blvd. 
Lenexa, KS  66219 
Tel:  (913) 599-8611        Fax:  (913) 599-8565 

 <http://www.ksu.edu>  



> -----Original Message-----
> From: Barry Margolin [mailto:barmar at genuity.net]
> Sent: Tuesday, November 06, 2001 3:27 PM
> To: comp-protocols-dns-bind at moderators.isc.org
> Subject: Re: Not able to resolve external names
> 
> 
> In article <9s9inm$ps7 at pub3.rc.vix.com>,
> John Ross  <john.ross at informix.com> wrote:
> >
> >DNS server on the box?  Yes.  Running?  Yes.
> >  
> >Pretty much ruled out firewall issues.  As I have already 
> talked on the
> >phone with uunet.
> >
> >Dig'ing @127.0.0.1 also produces a timeout.
> 
> I think it's time for you to put a sniffer on the LAN to see the DNS
> traffic.
> 
> -- 
> 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.
>