[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 231
  • Last Modified:

DNS not working properly on the WIN 2003

Hey Guys I have a wierd problem. DNS is not working properly on my Network. When I try to resolve another servers address, it says server does not exist (using NSLOOKUP). When I run an NSLOOKUP on the servers IP address, it return the name of the server, there by meaning the server exist. I checked the the forward and reverse dns table on the DNS server which is also the DC and both show the correct A record and the PTR record. Now this doesnt happen every time, it happens on sometimes and on random computer on our network

What could this mean???  
2 Solutions
If I understood.  
1) DNS is hosted on Windows 2003 DC (myserver1)
2) Checking the DNS table for the mydomain.local zone, you see an A Record for myserver2 with its IP address.  
3) At random times from a 3rd workstation. NSlookup to myserver2.mydomain.local returns no server found, but all other times it functions correctly.

If all those are correct, I would start with the DNS server's event viewer and look for any service restarts, dns errors.  It almost sounds like at times the dns service is unavailable.  

Some other things to check, look for bad lmhosts or hosts file entries that *Might* be messing with resolution.   Are the Workstations on DHCP, make sure your DHCP settings are correct(related to dns server addresses) and that there are no other DHCP servers on the network .  

Some basic things to check.

First check the clients. The clients should have their "Preferred DNS server" set to point to your Windows DNS server (normally the DC). No other DNS should be specified on the clients.

The Windows DNS server (Normally the DC) should point to itself as "Preferred DNS server", again no thther DNS should be specified.

In the DNS console, forwarding should be enabled and the address(es) of your ISPs DNS servers entered on the forwarders tab.

Clear the DNS server cache (on the DNS console) - right click and select clear cache
and the client cache (ipconfig /flushdns) before re-testing.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now