Thanks for the tip. The trace showed me lots of information. I know how far it got, but don't know what it was trying to do when it timed out. Here's the last bit of the DiG output: ;; Received 436 bytes from 127.0.0.1#53(127.0.0.1) in 2 ms ca. 172800 IN NS ca05.cira.ca. ca. 172800 IN NS ns-ext.isc.org. ca. 172800 IN NS ca02.cira.ca. ca. 172800 IN NS ca06.cira.ca. ca. 172800 IN NS ca04.cira.ca. ca. 172800 IN NS ca01.cira.ca. ;; Received 287 bytes from 193.0.14.129#53(K.ROOT-SERVERS.NET) in 797 ms 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 -----Original Message----- From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Paul Howarth Sent: Wednesday, October 06, 2004 11:49 AM To: For users of Fedora Core releases Subject: Re: Dig timeout on certain domains On Wed, 2004-10-06 at 19:11, Aaron O'Hara wrote: > All, > > I'm running FC1 with Bind and I'm having DNS issues. I'm using DiG > 9.2.2 and it doesn't work on domains I know to be valid: > > www.futureshop.ca > www.theweathernetwork.com > > When I DiG for those domains, I get the message "connection timed out; > no servers could be reached" after 12 seconds. Most other domains > will respond within 1 or 2 seconds. Both of these names resolve find from here in the UK. > What would cause DiG not to find a domain? Try: dig www.futureshop.ca +trace you'll see it making queries to the individual nameservers from the root downwards and that might give an indication of where the problem is. Paul. -- Paul Howarth <paul@xxxxxxxxxxxx> -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list __________ NOD32 1.885 (20041006) Information __________ This message was checked by NOD32 Antivirus System. http://www.nod32.com
