Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Im having DNS issues on my network. My DC is my DNS server and recently I configured a forwarder to My workstations are not working because they cannot resolve the domain controller name because of DNS. an ipconfig /all reveals that they know the IP of the DNS server is, but if I nslookup it forwards the request to and goes nowhere. I have since removed the forwarder, but still any nslookup requests on workstations are going to If I nslookup on the server it can resolve its name, but for some reason when it receives the same request from workstations it doesnt know what to do. All the A, CNAME records etc are correct. DHCP's DNS is set correctly, GPOs are correct (even though they cant refresh cos of this problem!), the servers network adapter has its DNS set to Just don't know.

I have a reverse lookup zone set, from a workstation I can do an nslookup of the DC using its name, but it seems to go through to resolve it, and it even displays the DCs IP address too! But still nslookup-ing the DCs IP address alone doesn't work.

The image posting link on here doesnt seem to work for me but I uploaded a screenshot of a nslookup from a workstation here:

enter image description here

thanks for the help!

Very confused.

share|improve this question
Do you have reverse DNS setup in the domain? Can you do an nslookup on the DNS name instead of the IP? – m1ke Feb 15 '11 at 7:04
Post the output of nslookup from one of the clients here. – joeqwerty Feb 15 '11 at 13:21

1 Answer 1

This issue has been resolved.

Looks like a crucial DNS suffix was missing/altered and was bringing down the whole system!

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.