Not able to resolve external names
John Ross
john.ross at informix.com
Tue Nov 6 20:01:51 UTC 2001
1) What if it times out? What does that mean? (well, besides that fact that
it isn't working :-( )
Server-in-question#./dig www.yahoo.com a
; <<>> DiG 2.0 <<>> www.yahoo.com a
;; res_send to server default -- 0.0.0.0: Connection timed out
If I specify a root name server by IP address @198.41.0.4
(A.ROOT-SERVERS.NET), or one of the DNS servers at my site, I get what you
would expect.
I have verified both with traceroute through port 53, and with uunet that
port 53 is not blocked at the firewall. This is really perplexing to me. I
am obviously not an expert, but I have never seen anything like this where I
have no clue as to what the problem is.
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 12:12 PM
> To: comp-protocols-dns-bind at moderators.isc.org
> Subject: Re: Not able to resolve external names
>
>
> In article <9s98ju$nak at pub3.rc.vix.com>,
> John Ross <john.ross at informix.com> wrote:
> >Could you give me a couple of examples to try? What am I
> looking for?
>
> Use "dig www.something.com a", where www.something.com is a name that
> should be found but fails (e.g. www.yahoo.com). If the
> result contains
> "status: NXDOMAIN", look in the Authority section of the reply. If it
> contains NS records for the root domain that aren't like
> A.ROOT-SERVERS.NET, or NS records for COM that aren't like
> A.GTLD-SERVERS.NET, then your cache has been poisoned.
>
> --
> 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
mailing list