nameserver ignoring udp queries ?
Kevin Darcy
kcd at daimlerchrysler.com
Tue Dec 10 18:15:21 UTC 2002
Rick wrote:
> Kevin Darcy wrote:
> > Rick wrote:
> >
> >
> >>Many months back my mozilla browser reported that it
> >>could not find www.yahoo.com or www.cnn.com. Other
> >>url's resolved with no problem. I solved the problem
> >>(I thought) by switching to the Pacific Root nameservers.
> >>Now the same thing is happening with them. I can't get
> >>a response unless I use TCP or advertize a larger
> >>buffer.
> >>
> >>It is my understanding that the resolver routines in
> >>glibc (mandrake 8.2) do not try TCP unless they receive
> >>a partial answer via udp. It appears to me that in the
> >>case of www.yahoo.com there is no response at all to
> >>udp queries.
> >>
> >> $ host www.yahoo.com
> >> ;; connection timed out; no servers could be reached
> >>
> >> $ host -T www.yahoo.com
> >> www.yahoo.com is an alias for www.yahoo.akadns.net
> >> www.yahoo.akadns.net has address 66.218.71.89
> >> /* more */
> >>
> >> $ dig www.yahoo.com
> >> ; <<>> DiG 9.2.1 <<>> www.yahoo.com
> >> ;; global options: printcmd
> >> ;; connection timed out; no servers could be reached
> >>
> >> $ dig www.yahoo.com +bufsize=65535
> >> ; <<>> DiG 9.2.1 <<>> www.yahoo.com +bufsize=65535
> >> ;; Got answer:
> >> ;; ->>>HEADER<<- opcode: QUERY, status: FORMERR, id: 24888
> >> ;; flags: qr rd ra; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
> >>
> >> ;; Query time: 204 msec
> >> ;; SERVER: 208.179.42.162#53(208.179.42.162)
> >> ;; WHEN: Mon Dec 9 12:35:55 2002
> >> ;; MSG SIZE rcvd:12
> >>
> >>I am assuming it is my problem since I cannot find anyone else
> >>complaining about it, but I don't have a clue.
> >>
> >>my /etc/resolv.conf:
> >> domain localdomain
> >> #pacific root nameservers
> >> nameserver 208.179.42.162
> >> nameserver 204.107.129.2
> >> nameserver 12.28.140.20
> >
> >
> > Run a local BIND nameserver with a official hints file, and you should be
> > fine. These "pacific root" nameservers are serving up bogus ".pacroot"
> > data, so who knows what other idiocy they may be up to...
> >
> >
> > - Kevin
> >
> >
> >
>
> I get the same results when I use the nameservers provided by
> my isp (earthlink)
I don't seem to be having any problem:
% dig www.yahoo.com @ns1.earthlink.net
; <<>> DiG 8.3 <<>> www.yahoo.com @ns1.earthlink.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 11, ADDITIONAL: 6
;; QUERY SECTION:
;; www.yahoo.com, type = A, class = IN
;; ANSWER SECTION:
www.yahoo.com. 23m4s IN CNAME www.yahoo.akadns.net.
www.yahoo.akadns.net. 4m59s IN A 66.218.71.84
www.yahoo.akadns.net. 4m59s IN A 66.218.71.85
www.yahoo.akadns.net. 4m59s IN A 66.218.71.86
www.yahoo.akadns.net. 4m59s IN A 66.218.71.87
www.yahoo.akadns.net. 4m59s IN A 66.218.71.88
www.yahoo.akadns.net. 4m59s IN A 66.218.71.89
www.yahoo.akadns.net. 4m59s IN A 66.218.71.80
www.yahoo.akadns.net. 4m59s IN A 66.218.71.81
www.yahoo.akadns.net. 4m59s IN A 66.218.71.83
;; AUTHORITY SECTION:
akadns.net. 16h19m16s IN NS NS1-159.AKAM.net.
akadns.net. 16h19m16s IN NS ZA.akadns.net.
akadns.net. 16h19m16s IN NS ZC.akadns.net.
akadns.net. 16h19m16s IN NS ZD.akadns.net.
akadns.net. 16h19m16s IN NS ZE.akadns.net.
akadns.net. 16h19m16s IN NS ZF.akadns.net.
akadns.net. 16h19m16s IN NS ZG.akadns.net.
akadns.net. 16h19m16s IN NS ZH.akadns.net.
akadns.net. 16h19m16s IN NS USE2.AKAM.net.
akadns.net. 16h19m16s IN NS USE3.AKAM.net.
akadns.net. 16h19m16s IN NS NS1-93.AKAM.net.
;; ADDITIONAL SECTION:
ZA.akadns.net. 1d11h23m23s IN A 216.32.65.105
ZC.akadns.net. 1d11h23m23s IN A 63.241.199.50
ZD.akadns.net. 1d11h23m23s IN A 206.132.160.36
ZE.akadns.net. 1d11h23m23s IN A 12.47.217.11
ZF.akadns.net. 1d11h23m23s IN A 63.215.198.79
ZG.akadns.net. 1d11h23m23s IN A 204.248.36.131
;; Total query time: 63 msec
;; FROM: fwiod01.is.chrysler.com to SERVER: ns1.earthlink.net 207.217.126.41
;; WHEN: Tue Dec 10 13:14:57 2002
;; MSG SIZE sent: 31 rcvd: 510
%
Looks like you have some sort of local networking problem.
- Kevin
More information about the bind-users
mailing list