nameserver ignoring udp queries ?

[Kevin Darcy]

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