Re: problem with resolving SOME EXTERNAL domains

<enesz@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 192.112.36.4#53(G.ROOT-SERVERS.NET) in 282 ms
>
> ./dig: couldn't get address for 'NS-NORVA.navy.mil': not found

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?

--
Ronan Flood <R.Flood@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)