DNS resolves only its own domain

Sergey Nikolaev snikolae at atlassoft.com
Fri May 19 15:54:05 UTC 2000


Hi, I am trying to migrate from bind-4.9.4-P1 to bind-8.2.2p5. I installed
bind-8.2.2P5 on a development server running Solaris 2.6. The installed
DNS server resolves the hostnames that are in its own database but not any
other. I tried to run named, which comes with Solaris, with the same
results. A DNS server on the development machine dosn't want resolve any
names but local ones.

I enabled debugging and below is a fragment of degugging information at
the time I ran an nslookup on www.sco.com.

datagram from [208.167.2.234].33361, fd 22, len 29; now Tue May 16
16:33:19 2000ns_req(from=[208.167.2.234].33361)
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48073
;; flags: rd; Ques: 1, Ans: 0, Auth: 0, Addit: 0
;; QUESTIONS:
;;      www.sco.com, type = A, class = IN

req: nlookup(www.sco.com) id 48073 type=1 class=1
req: found 'www.sco.com' as 'com' (cname=0)
np_parent(0x0) couldn't find root entry
findns: 13 NS's added for ''
ns_forw()


The root.cache file used on the dev. server is just the same as on the
production server.

Thanks for any help.

Sergey 






More information about the bind-users mailing list