Discussion Locked

DNS problems...

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have one Win2K server. It is, of course, our DHCP, DNS, PDC, Exchange, File, Print, and whatever else, server. It appears that I have screwed something up with the DNS settings. I know that's pretty broad. I'm hoping you can at least give me a place to start, though. Our 95/98 workstations are quick and responsive. Our XP machines have a pause when trying to open files, etc. I think that is related. When I run nslookup on an XP workstation, I get this:

C:>nslookup
*** Can't find server name for address 10.1.0.2: Non-existent domain
*** Default servers are not available
Default Server: UnKnown
Address: 10.1.0.2

The server is 10.1.0.2 When I do a ping by machine name, it works (i.e. "Ping SBS" gets "Pinging sbs.RRLAW.local [10.1.0.2] with...").

DNS IS running on the server, settings appear to be correct, but I'm obviously missing something. Any suggestions on where to start looking, or how to test further?

9 replies

by jose_12650

First thing first: Check your the TCP/IP properties on your network card to see if you have checked the option to Obtain IP Address Automatically and Obtain DNS Derver Address Automatically on your XP machine.

Then go to DHCP console ( start, programs, administrative tools, then click DHCP). Click your server (machine) and from the dropdown folders right click Scope Optiion, Configure Option, on the General Tab scroll down on 006 check it, on Data Entry (Server name, type your DNS Server Name and Click Resolve, you should be able to see IP 10.1.0.2, click apply.

by jaystar

The specific problem above with *** can't find server name for 10.1.0.2: Non-existent domain stems from the fact that you do not have the proper reverse-lookup domain configured. If I may ask, have you changed IP ranges recently? If you change IP ranges, you must create a new reverse lookup zone and move the registrations out of the old zone into the new one.

If you need help with this, feel free to contact me.

by justanadmin

Be sure you have a pointer record for the server in the reverse lookup zone. The lack of one can definitey cause this message.

by mlchin

The *** error is most probably due to a reverse dns zone error. You'll need to manually create a reverse dns zone. Reverse dns zone is not created automatically in Microsoft DNS. Once created make sure you have a PTR record created for the DNS server.

More importantly... is your forward lookups working fine? Can you "ping sbs.RRLAW.local" and get a reply? Try not to use "Ping SBS" cause sometimes that only resolves to the Netbios name.

Hope this helps.

This discussion is closed to new replies.