DNS timed out
Lou Goddard
lgoddard at camptv.com
Mon Dec 13 15:14:07 UTC 2004
Two of the GTLD servers have AAAA records now. There are other messages =
with
more detail. Have you tried searching the list?
-----Original Message-----
From: Rasheed [mailto:rasheed at anet.net.sa]
Sent: Monday, December 13, 2004 10:09 AM
To: bind-users at isc.org
Cc: Lou Goddard
Subject: RE: DNS timed out
I'm using a package one from www.sunfreeware.com ready one. And it is =
not
compiled with this option !!!
I'm running my DNS more than a year without problem. Why this happened =
in
last two days?
Rasheed
-----Original Message-----
From: Lou Goddard [mailto:lgoddard at camptv.com]=20
Sent: Monday, December 13, 2004 5:55 PM
To: Rasheed; bind-users at isc.org
Subject: RE: DNS timed out
You could recompile 9.2.2 with "--disable-ipv6"
-----Original Message-----
From: Rasheed [mailto:rasheed at anet.net.sa]
Sent: Monday, December 13, 2004 9:50 AM
To: bind-users at isc.org
Cc: Lou Goddard
Subject: RE: DNS timed out
I can't do it with my 9.2.2 version?
Rasheed
-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On =
Behalf
Of Lou Goddard
Sent: Monday, December 13, 2004 3:13 PM
To: Rasheed; bind-users at isc.org
Subject: RE: DNS timed out
Some of the gtld servers have IPv6 connectivity now. Your name server =
=3D
is
probably trying to contact them via IPv6 and failing. You could upgrade =
=3D
to 9.3.0
and start named with the "-4".
-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Rasheed
Sent: Monday, December 13, 2004 3:53 AM
To: bind-users at isc.org
Subject: DNS timed out
Hi,
=3D20
I'm facing a strange problem with my DNS sever. I'm running bind 9.2.2. =
=3D
I
have many complains from customers abut DNS timed out. I check it by =3D
myself
using nslookup from a client. The first request for MX for domain =3D
come.com
(test only) answered with timed out but second request for the same =3D
domain
get answers. I have made loglevel 3 and below you will find outputs. You =
=3D
can
see from below debug log in first request that there is time outage :-
=3D20
Dec 13 11:28:59.098 client: debug 3: client 212.93.196.38#4071: replace
Dec 13 11:29:03.706 client: debug 3: client 212.93.196.38#4071: send
And this not happing in the second one.
I didn't modified things lately.
=3D20
Thanks,
Rasheed
=3D20
###########################################
> set q=3D3Dmx
> come.com <First Request>
Server: ns2.awalnet.net.sa
Address: 212.93.192.5
=3D20
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to ns2.awalnet.net.sa timed-out
> come.com <Second Request>
Server: ns2.awalnet.net.sa
Address: 212.93.192.5
=3D20
come.com
primary name server =3D3D ns1.rjsnetworks.com
responsible mail addr =3D3D jai.rjsnetworks.com
serial =3D3D 2004050701
refresh =3D3D 900 (15 mins)
retry =3D3D 3600 (1 hour)
expire =3D3D 900 (15 mins)
default TTL =3D3D 900 (15 mins)
>exit
############################################
=3D20
=3D20
##################### First Request ##############################
Dec 13 11:28:59.097 client: debug 3: client 212.93.196.38#4070: UDP =3D
request
Dec 13 11:28:59.097 client: debug 3: client 212.93.196.38#4070: query
Dec 13 11:28:59.097 client: debug 3: client 212.93.196.38#4070: send
Dec 13 11:28:59.097 client: debug 3: client 212.93.196.38#4070: sendto
Dec 13 11:28:59.097 client: debug 3: client 212.93.196.38#4070: senddone
Dec 13 11:28:59.097 client: debug 3: client 212.93.196.38#4070: next
Dec 13 11:28:59.097 client: debug 3: client 212.93.196.38#4070: =3D
endrequest
Dec 13 11:28:59.098 client: debug 3: client 212.93.196.38#4071: UDP =3D
request
Dec 13 11:28:59.098 client: debug 3: client 212.93.196.38#4071: query
Dec 13 11:28:59.098 client: debug 3: client 212.93.196.38#4071: replace
Dec 13 11:29:03.706 client: debug 3: client 212.93.196.38#4071: send
Dec 13 11:29:03.706 client: debug 3: client 212.93.196.38#4071: sendto
Dec 13 11:29:03.706 client: debug 3: client 212.93.196.38#4071: senddone
Dec 13 11:29:03.706 client: debug 3: client 212.93.196.38#4071: next
Dec 13 11:29:03.706 client: debug 3: client 212.93.196.38#4071: =3D
endrequest
=3D20
##################### First Request ##############################
Dec 13 11:29:07.947 client: debug 3: client 212.93.196.38#4072: UDP =3D
request
Dec 13 11:29:07.947 client: debug 3: client 212.93.196.38#4072: query
Dec 13 11:29:07.947 client: debug 3: client 212.93.196.38#4072: send
Dec 13 11:29:07.947 client: debug 3: client 212.93.196.38#4072: sendto
Dec 13 11:29:07.947 client: debug 3: client 212.93.196.38#4072: senddone
Dec 13 11:29:07.947 client: debug 3: client 212.93.196.38#4072: next
Dec 13 11:29:07.947 client: debug 3: client 212.93.196.38#4072: =3D
endrequest
Dec 13 11:29:07.948 client: debug 3: client 212.93.196.38#4073: UDP =3D
request
Dec 13 11:29:07.948 client: debug 3: client 212.93.196.38#4073: query
Dec 13 11:29:07.948 client: debug 3: client 212.93.196.38#4073: send
Dec 13 11:29:07.948 client: debug 3: client 212.93.196.38#4073: sendto
Dec 13 11:29:07.948 client: debug 3: client 212.93.196.38#4073: senddone
Dec 13 11:29:07.948 client: debug 3: client 212.93.196.38#4073: next
Dec 13 11:29:07.948 client: debug 3: client 212.93.196.38#4073: =3D
endrequest
=3D20
More information about the bind-users
mailing list