Re: [CNS-NS #16701] DNS b0rk3n?

rossd@quantum.me.berkeley.edu via RT wrote:

> Hmmm... I was trying to hit www.namesys.com to forward
> someone the speed results of Reiser4 (WELL worth the trouble, btw).
> But it looks like the Campus DNS boxxen must be on a smoke break
> or something....
>
> rossd@rossd ~ $ dig www.namesys.com
> ; <<>> DiG 9.2.3 <<>> www.namesys.com
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
>
> but PacBell's DNS has it...
> rossd@rossd ~ $ dig @206.13.31.12 www.namesys.com
>
> ; <<>> DiG 9.2.3 <<>> @206.13.31.12 www.namesys.com
> ;; global options: printcmd
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49141
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
> ;; QUESTION SECTION:
> ;www.namesys.com. IN A
> ;; ANSWER SECTION:
> www.namesys.com. 49484 IN A 212.16.7.65
> ;; AUTHORITY SECTION:
> namesys.com. 49484 IN NS ns.namesys.com.
> namesys.com. 49484 IN NS ns0.comstar.ru.
> ;; ADDITIONAL SECTION:
> ns.namesys.com. 49484 IN A 212.16.7.65
> ns0.comstar.ru. 41525 IN A 212.248.0.3
> ns0.comstar.ru. 41525 IN A 195.210.128.3
> ;; Query time: 19 msec
> ;; SERVER: 206.13.31.12#53(206.13.31.12)
> ;; WHEN: Mon Jan 24 14:24:22 2005
> ;; MSG SIZE rcvd: 142
>
> and I can get other addresses from campus....
>
> rossd@rossd ~ $ dig www.yahoo.com
> ; <<>> DiG 9.2.3 <<>> www.yahoo.com
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62833
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 9, ADDITIONAL: 8
>
> ;; QUESTION SECTION:
> ;www.yahoo.com. IN A
> ;; ANSWER SECTION:
> www.yahoo.com. 219 IN CNAME www.yahoo.akadns.net.
> www.yahoo.akadns.net. 48 IN A 66.94.230.44
> www.yahoo.akadns.net. 48 IN A 66.94.230.48
> www.yahoo.akadns.net. 48 IN A 66.94.230.49
> www.yahoo.akadns.net. 48 IN A 66.94.230.50
> www.yahoo.akadns.net. 48 IN A 66.94.230.32, etc, etc....
>
> but I did notice this...
> rossd ~ $ nslookup www.namesys.com 128.32.206.12
> Note: nslookup is deprecated and may be removed from future releases.
> Consider using the `dig' or `host' programs instead. Run nslookup with
> the `-sil[ent]' option to prevent this message from appearing.
> ;; reply from unexpected source: 128.32.136.12#53, expected 128.32.206.12#53
> ;; Warning: ID mismatch: expected ID 63012, got 24375
> ;; reply from unexpected source: 128.32.136.12#53, expected 128.32.206.12#53
> ;; Warning: ID mismatch: expected ID 63012, got 24375
> ;; connection timed out; no servers could be reached
>
>
> Hope that helps... Reiser4 is definitely worth telling people about! :-)
>
> but i think it statistically anomalous to think it only this one site
> is problematic...
>
> Anyone else notice it?

Nobody else has noticed it, but I'll look into it. Usually when this
sort of thing happens, it's because there's something subtly wrong with
the domain in question, and it's effectively inadvertantly poisoning the
caches of the nameservers of everyone who tries to go there.

PacBell does something really weird with their nameservers and I need to
find out what that is, but it effectly changes the caching effects that
users see.

The nslookup results you see are probably due to the fact that the
servers are responding after nslookup has timed out, and that's
confusing nslookup as it cycles through all of the server addresses in
your resolv.conf.

michael

------------------------------------------------------------------------
The following was automatically added to this message by the list server:

For information about Micronet, including subscribing to
or unsubscribing from its mailing list and finding out
about upcoming meetings, please visit the Micronet Web site:
<http://micronet.berkeley.edu/>.
Received on Tue Jan 25 10:34:35 2005