problem with resolving SOME EXTERNAL domains
ronan at noc.ulcc.ac.uk
Wed Jun 8 21:42:21 UTC 2005
<enesz at bih.net.ba> wrote:
> NOT WORKING
> # ./dig navy.mil +trace
> navy.mil. 86400 IN NS NS-NORVA.navy.mil.
> navy.mil. 86400 IN NS NS-HAWAII.navy.mil.
> navy.mil. 86400 IN NS NS-NORFOLK.navy.mil.
> navy.mil. 86400 IN NS NS-SANDIEGO.navy.mil.
> navy.mil. 86400 IN NS NS-NAPLES.navy.mil.
> ;; Received 228 bytes from 18.104.22.168#53(G.ROOT-SERVERS.NET) in 282 ms
> ./dig: couldn't get address for 'NS-NORVA.navy.mil': not found
(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
Can you query those servers directly by IP address from dig, eg
ns-naples.navy.mil is 22.214.171.124, so
dig @126.96.36.199 usno.navy.mil. a +norec
should list the NS records for usno.navy.mil and the A records for those
;; ->>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 188.8.131.52
CHARON.usno.navy.mil. 86400 IN A 184.108.40.206
PSYCHE.usno.navy.mil. 86400 IN A 220.127.116.11
The other nameservers for navy.mil are 18.104.22.168, 22.214.171.124,
126.96.36.199 and 188.8.131.52, so you could try the above with them
Might as well ask: what's in your named.conf?
Ronan Flood <R.Flood at noc.ulcc.ac.uk>
working for but not speaking for
Network Services, University of London Computer Centre
(which means: don't bother ULCC if I've said something you don't like)
More information about the bind-users