Jason Staudenmayer wrote:

Sounds like a bad routing table. Like the resolve file is set right but the
return route for the packets is bad. Had something similar with a win2k box
and Pcanywhere. It would receive the first packet but couldn't return them.

A bad routing table on this Redhat v9 box, or a bad routing table on the next hop router?


I don't see how routing could be an issue: All other services (web, ssh, etc) work 100% from and to this box. The only problem is with DNS, and _only_ with www.apple.com, and www.yahoo.com.

Something someone else picked up:

Both www.apple.com and www.yahoo.com are CNAMEs for www.apple.com.akadns.net and www.yahoo.akadns.net respectively.

An attempt to connect to http://akadns.net returns a redirect to http://www.akadns.net, an address which does not exist.

Anybody heard of Akadns before? Anyone know why a Redhat v9 box cannot resolve their queries specifically?

Regards,
Graham
--

-----Original Message-----
From: Graham Leggett [mailto:[EMAIL PROTECTED] Sent: Friday, September 05, 2003 9:11 AM
To: [EMAIL PROTECTED]
Subject: DNS problems from the twilight zone



Hi all,


I have a Redhat v9 box that is incapable of resolving certain specific
DNS addresses, but it can resolve others. Addresses that work:

www.google.com
www.is.co.za
www.anazi.co.za

Addresses that do not work:

www.yahoo.com
www.apple.com

An attempt to resolve the packet looks like this:

[EMAIL PROTECTED] root]# dig www.yahoo.com @196.4.160.2

; <<>> DiG 9.2.1 <<>> www.yahoo.com @196.4.160.2
;; global options:  printcmd
;; connection timed out; no servers could be reached

When tcpdump is used to sniff the connection, the following is shown:

14:21:55.641265 168.209.124.18.32839 > 196.4.160.2.domain:  57497+ A?
www.yahoo.com. (31) (DF)
14:22:00.653797 168.209.124.18.32839 > 196.4.160.2.domain:  57497+ A?
www.yahoo.com. (31) (DF)

Two packets go out, nothing comes back.

When the next hop router is sniffed, it shows the packets go out, and it
shows packets being returned - the Linux box (or something) is dropping
the return packets before they reach tcpdump.

Anyone seen anything like this before?

Regards,
Graham


--
-----------------------------------------
[EMAIL PROTECTED]               "There's a moon
                                        over Bourbon Street
                                                tonight..."


-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to