Search Again:

Re: weird dns error resolving "www"

From: Len Conrad
Date: Saturday, September 22, 2001
Time: 12:18:41 pm


>Hi All: I have a domain I've been hosting for over a year...."gas2001.co=
m"
>
>I have an A record for the domain pointing to the webserver.
>
>I have a CNAME record for "www" pointing to the root A record

replace the CNAME with a A.

>suddenly browsers trying to connect to www.gas2001.com can't resolve thi=
s
>address.

; <<>> DiG 8.3 <<>> www.gas2001.com a
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 3
;; QUERY SECTION:
;; www.gas2001.com, type =3D A, class =3D IN

;; ANSWER SECTION:
www.gas2001.com. 1D IN CNAME gas2001.com.
gas2001.com. 1D IN A 206.20.122.72

;; AUTHORITY SECTION:
gas2001.com. 1D IN NS ns.idt.net.
gas2001.com. 1D IN NS ns1.ardentmicro.com.
gas2001.com. 1D IN NS ns2.ardentmicro.com.

;; ADDITIONAL SECTION:
ns.idt.net. 1d22h32m4s IN A 198.4.75.100
ns1.ardentmicro.com. 1D IN A 206.20.122.11
ns2.ardentmicro.com. 1D IN A 206.20.122.12

;; Total query time: 3974 msec

It took nearly 4 secs to resolve, queried from NJ, maybe there=B4s a=20
connectivity pb that is causing long delays that cause resolvers to timeo=
ut.

traceroute is fast enough to the www:

Lists# traceroute 206.20.122.72
traceroute to 206.20.122.72 (206.20.122.72), 30 hops max, 40 byte packets
1 host-66-40-138-41.flashhost.com (66.40.138.41) 0.221 ms 0.198=20
ms 0.332 ms
2 VLAN7.FMT6509-2.hostcentric.com (209.25.128.71) 0.795 ms 0.741=20
ms 0.677 ms
3 GigE4-2.FMT-2.hostcentric.com (66.40.24.101) 0.370 ms 0.293 ms 0.=
327 ms
4 GigE6-0.FMT-2.hostcentric.com (66.40.24.110) 0.829 ms 1.037 ms 0.=
781 ms
5 vlan5.paix-1.hostcentric.com (216.65.0.5) 0.915 ms 0.811 ms 0.823=
ms
6 64.124.50.162.maxim.com (64.124.50.162) 1.122 ms 0.827 ms 0.857 m=
s
7 sjc2-pao1-oc48-2.sjc2.above.net (208.185.175.161) 1.273 ms 1.339=20
ms 1.319 ms
8 core1-core4-oc48.sjc2.above.net (208.184.102.201) 1.422 ms 1.284=20
ms 1.610 ms
9 core6-sjc2-oc48.sjc1.above.net (216.200.0.177) 1.484 ms 1.397=20
ms 1.449 ms
10 core2-sjc1-oc3.sjc6.above.net (207.126.96.106) 1.849 ms 1.735=20
ms 1.966 ms
11 idt-above-10Mbps.maew.above.net (209.133.31.210) 2.980 ms 2.783=20
ms 2.708 ms
12 54-core-1-oc3-2-0.hck.idt.net (169.132.147.50) 71.787 ms 72.131=20
ms 72.584 ms
13 colo-1-fe-0-0.hck.idt.net (169.132.190.150) 72.037 ms 72.464=20
ms 72.074 ms
14 www.buvalue.com (206.20.122.72) 71.673 ms 71.580 ms 72.292 ms

but one of the DNS's isn=B4t responding:

traceroute to 206.20.122.12 (206.20.122.12), 30 hops max, 40 byte packets
1 host-66-40-138-41.flashhost.com (66.40.138.41) 0.222 ms 0.326=20
ms 0.155 ms
2 VLAN7.FMT6509-2.hostcentric.com (209.25.128.71) 0.922 ms 0.865=20
ms 0.567 ms
3 GigE4-2.FMT-2.hostcentric.com (66.40.24.101) 0.459 ms 0.430 ms 0.=
384 ms
4 GigE6-0.FMT-2.hostcentric.com (66.40.24.110) 0.959 ms 0.836 ms 0.=
781 ms
5 vlan5.paix-1.hostcentric.com (216.65.0.5) 0.918 ms 0.968 ms 0.890=
ms
6 64.124.50.162.maxim.com (64.124.50.162) 0.885 ms 0.855 ms 1.045 m=
s
7 sjc2-pao1-oc48-2.sjc2.above.net (208.185.175.161) 1.358 ms 1.418=20
ms 1.316 ms
8 core3-core4-oc48.sjc2.above.net (208.184.102.197) 1.864 ms 1.504=20
ms 1.415 ms
9 core6-sjc2-oc48-2.sjc1.above.net (208.184.102.205) 1.511 ms 1.405=20
ms 1.443 ms
10 core2-sjc1-oc3.sjc6.above.net (207.126.96.106) 1.898 ms 1.802=20
ms 2.090 ms
11 idt-above-10Mbps.maew.above.net (209.133.31.210) 2.739 ms 3.294=20
ms 3.028 ms
12 54-core-1-oc3-2-0.hck.idt.net (169.132.147.50) 72.472 ms 71.831=20
ms 72.123 ms
13 colo-1-fe-0-0.hck.idt.net (169.132.190.150) 72.561 ms 71.993=20
ms 72.144 ms
14 * * *
15 * * *
16 * * *
17 * * *

>Is there something wrong with my DNS config?

it sure looks like it:

Errors
----------------------------------------------------------------------
o The server "ns2.ardentmicro.com." did not reply
The server "ns2.ardentmicro.com." did not reply when it was
queried for the name "gas2001.com.". This indicates that the
server is not running, or it is currently unreachable.

o Non-authoritative data received from the server "ns.idt.net."
The server "ns.idt.net." is listed as being authoritative for the
domain, but it does not contain authoritative data for it.

o Only one of your name servers has autoritative data for the zone.
The server "ns1.ardentmicro.com." is the only server that has
authoritaive data for the zone. If this server becomes
unavailable, your domain will become inacessible.

Len
____________________________________________________________________
Men & Mice: QuickDNS - DNS Expert - DNS Training - DNS Consulting

DNS Classes: Denver Sep. 20-21, NYC Sep. 27-28, Toronto Oct. 18,19
Frankfurt Nov.21-23, London Nov. 26-28, Maidenhead Oct. 31-Nov 2
http://MenAndMice.com/DNS-training




Messages In This Thread:



Return to Digital Point Solutions' Home Page