Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm at home (COMCAST is the ISP). I can run nslookup and resolve IPs fine. When I run dig I receive "connection timed out: no servers could be reached"

I'm going to fireup a network trace but wondering if anyone else has seen this. Windows 7 is the OS, just doing some DNS lookups.

share|improve this question

closed as off topic by Jason Berg, EEAA, mailq, Shane Madden, Scott Pack Sep 24 '11 at 17:38

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

Since when does there exist a dig under Windows 7? – mailq Sep 23 '11 at 23:01
@mailq As long as Nicholas Fong has been providing great Win32 binaries. – Weaver Sep 23 '11 at 23:58
Migrate to – Andrew Case Sep 24 '11 at 4:22
up vote 4 down vote accepted

Did you copy resolv.conf from your dig directory to your %systemroot%\system32\drivers\etc directory? If not, that's your problem.

share|improve this answer

Sounds like it could be an issue with the firewall blocking the connection coming back from DNS. You could try to disable the firewall and test the dig again to see if it succeeds.

share|improve this answer
If nslookup works, then it can't be a firewall issue. – mailq Sep 23 '11 at 23:03
@mailq actually, it could be a firewall issue, if nslookup does a query over UDP and dig does it over TCP (which is often what happens, because dig is requesting more information than a single packet response will allow). – Jed Daniels Sep 23 '11 at 23:44

This is either a TCP/UDP blocking issue or an IPv6 issue. Do you have a firewall? It might be blocking the TCP DNS queries that dig is generating. Alternately, it might be attempting to do v6 lookups (or might be attempting v4 lookups when v6 are the only ones being allowed through). But I'd put my money on TCP being blocked for DNS, which dig often uses because it requests much more information in a query than just the domain name->IP mapping.

share|improve this answer

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