Dig timeout on certain domains
Aaron O'Hara
ajeo at globalreachsoftware.com
Wed Oct 6 23:07:44 UTC 2004
Alexander,
I did as you said running:
/usr/sbin/tcpdump -X port 53
tcpdump: listening on eth0
And then running the 2 DiG statements.
I then quit the tcpdump command and got:
0 packets received by filter
0 packets dropped by kernel
I also ran DiG with domains that worked fine, and tcpdump didn't act any
different.
What should I try next?
Aaron
-----Original Message-----
From: fedora-list-bounces at redhat.com [mailto:fedora-list-bounces at redhat.com]
On Behalf Of Alexander Dalloz
Sent: Wednesday, October 06, 2004 3:51 PM
To: For users of Fedora Core releases
Subject: Re: Dig timeout on certain domains
Am Do, den 07.10.2004 schrieb Aaron O'Hara um 0:33:
> futureshop.ca. 86400 IN NS dns2.cidc.telus.com.
> futureshop.ca. 86400 IN NS dns1.cidc.telus.com.
> ;; Received 87 bytes from 129.33.164.84#53(ca05.cira.ca) in 2442 ms
>
> ;; connection timed out; no servers could be reached
>
> Why did it timeout?
>
> Aaron
Run "dig @dns1.cidc.telus.com futureshop.ca" and too querying the
dns2.cidc.telus.com. When doing so run in a different terminal / console
"tcpdump -X port 53". Do you have anything running (iptables) which could
block port 53 both UDP _and_ TCP?
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora
GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp Serendipity 00:47:58 up 7
days, 3:14, load average: 1.06, 1.18, 1.26
__________ NOD32 1.885 (20041006) Information __________
This message was checked by NOD32 Antivirus System.
http://www.nod32.com
More information about the fedora-list
mailing list