Re: problem with resolving SOME EXTERNAL domains

OK

I installed new 9.3.1 Bind to my slave DNS server (195.222.32.20). I
found BIND on isc.org, the file was bind-9.3.1.tar.gz, i done
../configure , make and it seems that BIND works.

But my problem with external domains is not solved. (all i get from this
is new version of dig 9.3 with trace option implmented).

So, here are dig outputs for domain which works and domains not working:

////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////
# ./dig cnn.com +trace

; <<>> DiG 9.3.1 <<>> cnn.com +trace
;; global options: printcmd
.. 509527 IN NS L.ROOT-SERVERS.NET.
.. 509527 IN NS M.ROOT-SERVERS.NET.
.. 509527 IN NS A.ROOT-SERVERS.NET.
.. 509527 IN NS B.ROOT-SERVERS.NET.
.. 509527 IN NS C.ROOT-SERVERS.NET.
.. 509527 IN NS D.ROOT-SERVERS.NET.
.. 509527 IN NS E.ROOT-SERVERS.NET.
.. 509527 IN NS F.ROOT-SERVERS.NET.
.. 509527 IN NS G.ROOT-SERVERS.NET.
.. 509527 IN NS H.ROOT-SERVERS.NET.
.. 509527 IN NS I.ROOT-SERVERS.NET.
.. 509527 IN NS J.ROOT-SERVERS.NET.
.. 509527 IN NS K.ROOT-SERVERS.NET.
;; Received 340 bytes from 195.222.32.20#53(195.222.32.20) in 1 ms

com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
;; Received 497 bytes from 198.32.64.12#53(L.ROOT-SERVERS.NET) in 202 ms

cnn.com. 172800 IN NS twdns-01.ns.aol.com.
cnn.com. 172800 IN NS twdns-02.ns.aol.com.
cnn.com. 172800 IN NS twdns-03.ns.aol.com.
cnn.com. 172800 IN NS twdns-04.ns.aol.com.
;; Received 188 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 130 ms

cnn.com. 300 IN A 64.236.24.28
cnn.com. 300 IN A 64.236.16.20
cnn.com. 300 IN A 64.236.16.52
cnn.com. 300 IN A 64.236.16.84
cnn.com. 300 IN A 64.236.16.116
cnn.com. 300 IN A 64.236.24.4
cnn.com. 300 IN A 64.236.24.12
cnn.com. 300 IN A 64.236.24.20
cnn.com. 600 IN NS twdns-04.ns.aol.com.
cnn.com. 600 IN NS twdns-01.ns.aol.com.
cnn.com. 600 IN NS twdns-02.ns.aol.com.
cnn.com. 600 IN NS twdns-03.ns.aol.com.
;; Received 252 bytes from 149.174.213.151#53(twdns-01.ns.aol.com) in
154 ms

////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////
NOT WORKING

# ./dig navy.mil +trace

; <<>> DiG 9.3.1 <<>> navy.mil +trace
;; global options: printcmd
.. 509493 IN NS G.ROOT-SERVERS.NET.
.. 509493 IN NS H.ROOT-SERVERS.NET.
.. 509493 IN NS I.ROOT-SERVERS.NET.
.. 509493 IN NS J.ROOT-SERVERS.NET.
.. 509493 IN NS K.ROOT-SERVERS.NET.
.. 509493 IN NS L.ROOT-SERVERS.NET.
.. 509493 IN NS M.ROOT-SERVERS.NET.
.. 509493 IN NS A.ROOT-SERVERS.NET.
.. 509493 IN NS B.ROOT-SERVERS.NET.
.. 509493 IN NS C.ROOT-SERVERS.NET.
.. 509493 IN NS D.ROOT-SERVERS.NET.
.. 509493 IN NS E.ROOT-SERVERS.NET.
.. 509493 IN NS F.ROOT-SERVERS.NET.
;; Received 356 bytes from 195.222.32.20#53(195.222.32.20) in 1 ms

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
#
////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////


Other DNS server (and dnsstuff.com also) can resolve NS-NORVA.navy.mil.

Any sugestions please?