problem with resolving SOME EXTERNAL domains

enesz at bih.net.ba enesz at bih.net.ba
Mon Jun 13 07:26:15 UTC 2005


Hi again,
 
<Ronan Flode> wrote:
<
Hmm.
 
(Question to group/list: does dig 9.3.1 rely on the configured resolver,
using gethostbyname or similar, to resolve the NS names to addresses,
ignoring any glue A in additional sections?  I've seen something that
does)
 
Can you query those servers directly by IP address from dig, eg
ns-naples.navy.mil is 138.180.5.138, so
 
dig @138.180.5.138 usno.navy.mil. a +norec
 
should list the NS records for usno.navy.mil and the A records for those
servers:
 
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64477
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 3
 
;; QUESTION SECTION:
;usno.navy.mil.               IN    A
 
;; AUTHORITY SECTION:
usno.navy.mil.          86400 IN    NS    METIS.usno.navy.mil.
usno.navy.mil.          86400 IN    NS    CHARON.usno.navy.mil.
usno.navy.mil.          86400 IN    NS    PSYCHE.usno.navy.mil.
 
;; ADDITIONAL SECTION:
METIS.usno.navy.mil.    86400 IN    A     198.116.61.5
CHARON.usno.navy.mil.   86400 IN    A     199.211.133.5
PSYCHE.usno.navy.mil.   86400 IN    A     192.5.41.214
 
 
The other nameservers for navy.mil are 205.56.138.34, 205.56.150.18,
138.143.200.2 and 192.245.206.2, so you could try the above with them
too.
 
Might as well ask: what's in your named.conf?
>
 
After flushing DNS cache with rndc flush, i tried to resolve with IP
adresses of navy.mil DNS servers, like this:
 
 
# ./dig @138.180.5.138 usno.navy.mil. a +norec
 
; <<>> DiG 9.3.1 <<>> @138.180.5.138 usno.navy.mil. a +norec
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached
# 
# 
# ./dig @205.56.138.34 usno.navy.mil. a +norec
 
; <<>> DiG 9.3.1 <<>> @205.56.138.34 usno.navy.mil. a +norec
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached
# 
# 
# ./dig @205.56.150.18 usno.navy.mil. a +norec
 
; <<>> DiG 9.3.1 <<>> @205.56.150.18 usno.navy.mil. a +norec
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached
# 
# ./dig @138.143.200.2 usno.navy.mil. a +norec
 
; <<>> DiG 9.3.1 <<>> @138.143.200.2 usno.navy.mil. a +norec
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached
# 
# 
# ./dig @192.245.206.2 usno.navy.mil. a +norec
 
; <<>> DiG 9.3.1 <<>> @192.245.206.2 usno.navy.mil. a +norec
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached
#
 
As you can see, NOTHING again.
 
Is this a network problem, or..?
Possible network problems on communication with root DNS servers?
 
Please, do you have sugestions?
 
Thanks
 
P.S I already sent my named.conf



More information about the bind-users mailing list