DNS not resolving a domain

[bizzaro]

I am running bind 9.2.4. I am unable to perform a lookup on a domain. No complaints of any other domain. I also tried to resolve this domain from several other places on the Internet and it works fine. Any ideas??

NANS01LX:~# dig tri-c.edu

; <<>> DiG 9.2.4 <<>> tri-c.edu
;; global options: printcmd
;; connection timed out; no servers could be reached

NANS01LX:~# nslookup tri-c.edu
;; connection timed out; no servers could be reached

NANS01LX:~# dig google.com

; <<>> DiG 9.2.4 <<>> google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16826
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 300 IN A 64.233.167.99
google.com. 300 IN A 64.233.187.99
google.com. 300 IN A 72.14.207.99

;; AUTHORITY SECTION:
google.com. 10782 IN NS ns2.google.com.
google.com. 10782 IN NS ns3.google.com.
google.com. 10782 IN NS ns4.google.com.
google.com. 10782 IN NS ns1.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 10038 IN A 216.239.32.10
ns2.google.com. 10038 IN A 216.239.34.10
ns3.google.com. 10038 IN A 216.239.36.10
ns4.google.com. 10038 IN A 216.239.38.10

;; Query time: 57 msec
;; SERVER: 168.98.65.5#53(168.98.65.5)
;; WHEN: Thu Sep 25 14:52:54 2008
;; MSG SIZE rcvd: 212

 

[elgrandeperro]

Can you get tri-c.edu's NS servers?

dig -t ns tri-c.edu


Do a traceroute for 141.110.238.51 or 52 (tri-c.edu's nameservers).

I get to hop 13 before it gets blocked:


6 hagg-03-ge-0-0-0-460.clmd.twtelecom.net (64.129.246.132) 50.154 ms 48.724 ms 48.594 ms
7 clmbs-r0-ge-0-0-0s855.bb.oar.net (199.18.0.18) 41.725 ms 41.290 ms 41.418 ms
8 clmbn-r2-ge-0-0-4s100.core.oar.net (199.218.38.22) 41.291 ms 38.890 ms 38.972 ms
9 clmbn-r0-xe-1-3-0s190.core.oar.net (199.218.38.45) 39.248 ms 38.907 ms 39.085 ms
10 clevs-r0-xe-1-1-0s100.core.oar.net (199.218.38.185) 42.826 ms 42.934 ms 43.778 ms
11 clevq-r5-ge-1-3-0s110.bb.oar.net (199.218.39.10) 44.088 ms 44.160 ms 44.144 ms
12 ccc-r2-se6-0.cpe.oar.net (199.18.113.146) 55.401 ms 55.420 ms 55.976 ms
13 ccc-nomad-eth2.cleveland.oar.net (199.18.114.70) 54.744 ms 54.841 ms 54.887 ms

 

[bizzaro]

Here is what I get. I did the same on another Internet DNS server that I have access to and it all looks fine.

# dig -t ns tri-c.edu

; <<>> DiG 9.2.4 <<>> -t ns tri-c.edu
;; global options: printcmd
;; connection timed out; no servers could be reached

This is as far as I get before it gets blocked:
4 500.Serial2-6.GW7.CLE1.ALTER.NET (157.130.125.5) 1.801 ms 1.845 ms 3.620 ms
5 0.so-0-2-1.XL2.CLE1.ALTER.NET (152.63.27.114) 1.495 ms 1.600 ms 1.577 ms
6 0.so-3-1-2.XT2.CHI2.ALTER.NET (152.63.64.198) 13.152 ms 17.645 ms 10.793 ms
7 0.so-7-0-0.BR1.CHI2.ALTER.NET (152.63.66.69) 10.674 ms 10.787 ms 11.101 ms
8 POS1-2-2488M.ar2.CHI2.gblx.net (64.215.195.137) 27.241 ms 13.075 ms 17.596 ms
9 Onecleveland.ge-3-0-0.ar2.cle1.gblx.net (67.17.211.250) 28.303 ms 20.808 ms 21.100 ms
10 208.48.253.98 (208.48.253.98) 21.770 ms 30.245 ms 23.754 ms

 

[elgrandeperro]

Is your root cache out of date? Have you restarted your DNS server?

Dig should not have to go to tri-c.edu to get the NS info...

 

[bizzaro]

Yes, BIND was restarted. How do I tell if my root cache is out of date?