Bind Help - NS Lookups timeout
Darren Nay
dnay at libertyisp.com
Thu Feb 19 17:43:51 UTC 2004
Yes, dig fails too. The reason that you are able to resolve now is because we put "forwarders" into our options in named.conf so that we could get it working in the interim.
Try ns2.ionosphere.net .. I've taken the forwardes off of it for now. This is what I get with dig.
dns2-grv1:/etc/namedb # dig @208.253.183.36 covad.net
; <<>> DiG 8.3 <<>> @208.253.183.36 covad.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; res_nsend to server 208.253.183.36 208.253.183.36: Connection timed out
dns2-grv1:/etc/namedb # dig @208.253.183.36 yahoo.com
; <<>> DiG 8.3 <<>> @208.253.183.36 yahoo.com
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5
;; QUERY SECTION:
;; yahoo.com, type = A, class = IN
;; ANSWER SECTION:
yahoo.com. 30M IN A 66.218.71.198
;; AUTHORITY SECTION:
yahoo.com. 2D IN NS ns1.yahoo.com.
yahoo.com. 2D IN NS ns2.yahoo.com.
yahoo.com. 2D IN NS ns3.yahoo.com.
yahoo.com. 2D IN NS ns4.yahoo.com.
yahoo.com. 2D IN NS ns5.yahoo.com.
;; ADDITIONAL SECTION:
ns1.yahoo.com. 1d4h8m47s IN A 66.218.71.63
ns2.yahoo.com. 1d4h8m47s IN A 66.163.169.170
ns3.yahoo.com. 1d4h8m47s IN A 217.12.4.104
ns4.yahoo.com. 1d4h8m47s IN A 63.250.206.138
ns5.yahoo.com. 1d4h8m47s IN A 216.109.116.17
;; Total query time: 33 msec
;; FROM: dns2-grv1 to SERVER: 208.253.183.36 208.253.183.36
;; WHEN: Thu Feb 19 12:37:36 2004
;; MSG SIZE sent: 27 rcvd: 222
Thanks,
Darren
Darren
----- Original Message -----
From: David Botham
To: Darren Nay
Cc: bind-users at isc.org ; bind-users-bounce at isc.org
Sent: Thursday, February 19, 2004 12:32 PM
Subject: Re: Bind Help - NS Lookups timeout
bind-users-bounce at isc.org wrote on 02/19/2004 12:23:23 PM:
[clip...]
> Try doing an nslookup (or dig) --using-- ns1.ionosphere.net as your name
> server, and lookup the A records for covad.net, then try to do the same thing
> looking up the A records for yahoo.com.
>
; <<>> DiG 9.2.2 <<>> www.ibm.com @208.253.183.35
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION:
;www.ibm.com. IN A
;; ANSWER SECTION:
www.ibm.com. 469 IN A 129.42.17.99
www.ibm.com. 469 IN A 129.42.18.99
www.ibm.com. 469 IN A 129.42.19.99
www.ibm.com. 469 IN A 129.42.20.99
www.ibm.com. 469 IN A 129.42.21.99
www.ibm.com. 469 IN A 129.42.16.99
;; AUTHORITY SECTION:
ibm.com. 491 IN NS ns.almaden.ibm.com.
ibm.com. 491 IN NS internet-server.zurich.ibm.com.
ibm.com. 491 IN NS ns.austin.ibm.com.
ibm.com. 491 IN NS ns.watson.ibm.com.
;; ADDITIONAL SECTION:
ns.almaden.ibm.com. 71998 IN A 198.4.83.35
internet-server.zurich.ibm.com. 106222 IN A 195.176.20.204
ns.austin.ibm.com. 70191 IN A 192.35.232.34
ns.watson.ibm.com. 34890 IN A 129.34.20.80
;; Query time: 160 msec
;; SERVER: 208.253.183.35#53(208.253.183.35)
;; WHEN: Thu Feb 19 12:29:53 2004
;; MSG SIZE rcvd: 310
C:\Documents and Settings\DBotham.IBMT3044>dig yahoo.com @208.253.183.35
; <<>> DiG 9.2.2 <<>> yahoo.com @208.253.183.35
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5
;; QUESTION SECTION:
;yahoo.com. IN A
;; ANSWER SECTION:
yahoo.com. 943 IN A 66.218.71.198
;; AUTHORITY SECTION:
yahoo.com. 117015 IN NS ns1.yahoo.com.
yahoo.com. 117015 IN NS ns2.yahoo.com.
yahoo.com. 117015 IN NS ns3.yahoo.com.
yahoo.com. 117015 IN NS ns4.yahoo.com.
yahoo.com. 117015 IN NS ns5.yahoo.com.
;; ADDITIONAL SECTION:
ns1.yahoo.com. 170275 IN A 66.218.71.63
ns2.yahoo.com. 170275 IN A 66.163.169.170
ns3.yahoo.com. 170275 IN A 217.12.4.104
ns4.yahoo.com. 170275 IN A 63.250.206.138
ns5.yahoo.com. 170275 IN A 216.109.116.17
;; Query time: 130 msec
;; SERVER: 208.253.183.35#53(208.253.183.35)
;; WHEN: Thu Feb 19 12:30:01 2004
;; MSG SIZE rcvd: 222
C:\Documents and Settings\DBotham.IBMT3044>dig redhat.com @208.253.183.35
; <<>> DiG 9.2.2 <<>> redhat.com @208.253.183.35
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
;; QUESTION SECTION:
;redhat.com. IN A
;; ANSWER SECTION:
redhat.com. 300 IN A 66.187.232.50
;; AUTHORITY SECTION:
redhat.com. 600 IN NS ns1.redhat.com.
redhat.com. 600 IN NS ns2.redhat.com.
redhat.com. 600 IN NS ns3.redhat.com.
;; ADDITIONAL SECTION:
ns1.redhat.com. 117714 IN A 66.187.233.210
ns2.redhat.com. 117714 IN A 66.187.224.210
ns3.redhat.com. 117714 IN A 66.187.229.10
;; Query time: 290 msec
;; SERVER: 208.253.183.35#53(208.253.183.35)
;; WHEN: Thu Feb 19 12:30:11 2004
;; MSG SIZE rcvd: 156
C:\Documents and Settings\DBotham.IBMT3044>dig covad.net @208.253.183.35
; <<>> DiG 9.2.2 <<>> covad.net @208.253.183.35
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;covad.net. IN A
;; ANSWER SECTION:
covad.net. 300 IN A 63.65.120.40
;; AUTHORITY SECTION:
covad.net. 272 IN NS ns2.covad.net.
covad.net. 272 IN NS ns1.covad.net.
;; ADDITIONAL SECTION:
ns2.covad.net. 169868 IN A 66.134.199.12
ns1.covad.net. 169868 IN A 66.134.199.11
;; Query time: 200 msec
;; SERVER: 208.253.183.35#53(208.253.183.35)
;; WHEN: Thu Feb 19 12:30:25 2004
;; MSG SIZE rcvd: 120
All seems ok from here. Are you sure "dig" fails from your end, and it is not just nslookup. It is known to have many issues.
Dave...
>[clip...]
More information about the bind-users
mailing list