Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a Windows 2008 standard server which can ping by hostname and give me the proper IP address back however if I try to do an nslookup on the hostname I receive:

server: nmgdc1.nmg.local
Address 192.168.1.10
DNS request timed out. timeout was 2 seconds.
DNS request timed out. timeout was 2 seconds.
*** Request to nmgdc1.nmg.local timed-out

I can get to the website fine through a web browser and can do a successful nslookup from a different client. Any ideas?

share|improve this question

5 Answers 5

As people have been pointing out your DNS server on 192.168.1.10 is not setup correctly or is not the right DNS server.

However the name can still be resolved by windows, probably using what is called NetBIOS over TCP/IP that works like an automatic DNS server system with auto server discovery on a LAN but doesn't scale well and is a bit hit and miss on it actually working.

share|improve this answer

Check the DNS Server entries on the problematic host. Chances are, it's not using the same DNS server as everything else that's working correctly.

share|improve this answer
    
I have 1 server and 3 computers at this location and none of them can do an nslookup on the website however from some of my other clients that I manage I can nslookup fine... the server nmgdc1 is my actual DNS server... –  Joshuah Feb 16 '12 at 22:49

If none of the machines on you LAN can complete a nslookup, then it's likely your local DNS can't resolve the hostname properly. It could be an issue with your DNS server, or with just the records for that host.

I would try to nslookup other local hosts, to see if the LAN DNS is functioning. You could also try to nslookup the hostname in question on a public DNS i.e. nslookup targetHost 208.67.222.222 (openDNS), though it sounds like public resolution is working fine.

share|improve this answer
    
If i do a nslookup targethost 208.67.222.222 than I get the proper IPs back. If I try to a local IP address on the network I get: Server: nmgdc1.nmg.local Address: 192.168.1.10 | *** nmgdc1.nmg.local can't find 192.168.1.150: Non-existent domain. –  Joshuah Feb 17 '12 at 2:10
    
Another thing I found is for some reason the server keeps adding a forwarder of 10.100.1.10 even though my ip address is 192.168.1.10. I deleted the forwarder and it seems to re-add itself some how... –  Joshuah Feb 17 '12 at 2:28

This article is from the Windows 2000 TechNet, but the principles and actions should still apply. It's got great troubleshooting and workflow steps to help you identify DNS resolution issues. Keep in mind, nslookup is kind've a PITA if reverse zones aren't established.

share|improve this answer

I feel like your DNS server is not properly set up on the .10 address. My guess is that your TCP/IP stack is using multiple DNS servers and one of them has pointed to the outside world. Go back and reconfigure your .10 address to your outside DNS servers.

share|improve this answer

Your Answer

 
discard

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.