Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS Setup on Windows Server 2003

Status
Not open for further replies.

up2speed

Technical User
Oct 23, 2003
2
US
Hello Everyone,

I am new to the forum, so please bear with me.

We are a small company running a Win Server 2k3 DC and a Win 2K member server for IIS. We wish to make the 2003 server a stand-alone DNS server that does not rely on the dns servers from our ISP, and only points to itself for DNS resolution. All is working well with the exception of two items. One, we cannot resolve our own web address which is hosted by our ISP. We have no problem with name resolution to any other domain name. We do have our domain suffix on our 2k3 server set to the same suffix as our web address. I am wondering if that is causing the conflict. Any suggetions would be appreciated.

Second, and on the same subject. If I run nslookup from a command line of any of your workstations or the 2 servers, the following message first appears:

"Can't find the domain server for the address 10.10.1.5: Non-existant domain"

10.10.1.5 is the IP of our DNS server. So nslookup cannot resolve the FQDN of our DNS Server. Again, any thoughts or suggestions are greatly approciated.

Thanks in advance

up2speed
 
How is your dns setup as far as A records and such. What shows up in the event logs on the server?

Glen A. Johnson
"Fall seven times, stand up eight."
Proverb

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
 
Hi Glen,

The DNS Logs have 2 items of concern, but I do not know if the entries are related to this problem. The first is:

"The DNS server could not signal the service "NAT". The error was 1168. There may be interoperability problems between the DNS service and this service."

The second one is:

"The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include:

1) No zones are configured for scavenging by this server.
2) A scavenging cycle was performed within the last 60 minutes.
3) An error occurred during scavenging.

The next scavenging cycle is scheduled to run in 0 hours.

The event data will contain the error code if there was an error during the scavenging cycle."

Hope this helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top