Not able to resolve external names
Barry Margolin
barmar at genuity.net
Mon Nov 5 22:44:13 UTC 2001
In article <9s74gg$5qr at pub3.rc.vix.com>,
John Ross <john.ross at informix.com> wrote:
>I am having a problem with BIND 4.9x. Just recently it has decided to not
>resolve external names (ie www.yaho.com <http://www.yaho.com> , etc.).
>Internal names resolve correctly, but external names just time out, or
>resolve minutes later. I have checked my connectivity to the root servers
>and I can both ping by address, and traceroute via port 53, so it appears
>that I can reach them. I recently pulled a copy of the current root
>servers, so that should be correct. I am pulling my hair out over this one,
>because unless I am missing something, everything looks fine.
If you're using BIND 4.x, the source port of queries that it sends out will
be 53. Maybe you have a firewall that's blocking inbound UDP to port 53.
--
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