dns nslookup problem

[Guest_imported]

I set up dns on my win2k ads with a standard primary in both my forward and reverse zones, checked allow dynamic updates in both zones and went to the properties sheet for my servers record that was created in the forward zone. I checked the update ptr box and clicked ok. after that I restarted the dns service. When I use nslookup it says that it can't resolve the IP of my dns server to a name, so I checked the .dns file and it had no IP for the entry, it was using @ in place of it. I then went to the name servers page of my reverse zone's properties and saw it had no IP listed next to its name either. I clicked edit and used the resolve button to no avail. I'm not sure what my next step is in solving this problem. Could use some advice. =)

 

[tertone100]

Weird, check your NIC, and then check wheather the server contains the 1.0.0.127.in-add.arpa zone (if the simple test fails). Select advanced from the view menu in the dns console. In the console tree,select reverse lookup zones, and confirm that it is there. It is created by default. If it is not there then the registry of the dns server may have been edited before dns was installed. If the dns server fails the simple thes then it will fail the recursive test.read up on the nslookup command, set querytype=NS (can't remember). You may want to un-install then re-install the dns server.

 

[tlcscousin]

Should actually be active directory integrated forward lookup zones if you are running DNS on the server and it is an active directory machine.
If you then want to be able to resolve names off the Internet you would delete the root zone entry and enable forwarders.

 

[tertone100]

Before you delite your root zone configure your router as a dns proxy. You may or may not need to delite your root zone, it depends on your routing.If your domain is active directory,i aggree with shovel204