I do an 'nslookup' from my workstation which was working allright until recently when I played just a bit with my Netware 5.1, SP8 patched, edirectory 8.7.3.4 installed Netware DNS/DHCP Management Console: Now when I do an nslookup for cnn.com from my workstation: The load 'named -v' console output on my Netware DNS Server is: ***QH_Proc:query recieved from <my station IP> QH_ns_req: Query for (cnn.com.lux.edu) of type a req_query_try_find_nonauth: look for (cnn.com.lux.edu) in non authoritative cache no referral found in authoritative cache for (cnn.com.lux.edu) send a udp reply to <my station ip> ***QH_Proc:query recieved from <my station IP> QH_ns_req: Query for cnn.com of type a re_query_noauth: look for (cnn.com) in non authoritative cache re_query_noauth: cnn.com not found in non authoritative cache finddns: no Root nameserver for class 1 req_query_nonauth_fetchns:findns - case SERVFAIL:failed! send a udp reply to <my station ip> Then using ns lookup, if I try to resolve a name for which the current Netware DNS is the designate primary (say zone :lux.edu) The console output is: ***QH_Proc:query recieved from <my station IP> QH_ns_req: Query for (fs01.lux.edu) of type a Domain Name (fs01.lux.edu) found in authoritative cache zone 'lux.edu' Send a udp reply to <my station ip> Configuration is very simple. I have this DNS/DHCP server serving 'lux.edu' and my primary (corporate) DNS Server IP address configured in the 'Forwarding List ' tab - say (192.165.50.30) All I did was create a test entry in RootServerInfo and within my designated Zone and deleted it later. The forwarding has stopped working since then.

Hi magnet, the easiest way is to create a new RootServerInfo. Take a look at your servers sys:\etc folder. Maybe there is a copy of the old RootServerInfo named rootsrvr.dat or RootServerInfo, without extention. You can import this file from DNSDHCP console. Don't forget to delete all entries under RootServerInfo in DNSDHCP console, before you do the import. Paul