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 have a server running Windows Server 2012 and it only has the Hyper-V role. I have a VM also running Windows Server 2012 and it has the Active Directory: Directory Services and DNS ([]) roles. It has been promoted to a domain controller for [].

In the virtualization host I have joined the domain successfully. On a laptop on the network, it can ping my DNS that is inside the VM on the virtualization host. However, it can't resolve anything through the DNS.

I figured it was a firewall issue where the DNS had the firewall allow rule, but the virtualization host did not. I added that, but it didn't fix the issue.

On my laptop, I get "UnKnown can't find []: No response from server" immediately. There's no time out, it just comes back right away.

What have I overlooked?

share|improve this question

migrated from Sep 29 '12 at 22:51

This question came from our site for professional and enthusiast programmers.

@KenWhite Agreed. I forgot about that. They all look the same sometimes. Too bad there's not an easy way to move your posts or close them yourself without voting. – Michael J. Gray Sep 29 '12 at 21:55
Michael, you can flag it for the moderators, and ask them to move it for you. – Ken White Sep 29 '12 at 21:57
Is your laptop pointed toward the correct nameserver (ipconfig /all)? Do you get the error when you query the nameserver directly (nslookup NAMSERVER_IP)? – Ansgar Wiechers Sep 29 '12 at 23:20
@AnsgarWiechers Yes it's pointed to the correct nameserver. I do get the same error when using nslookup to query that nameserver directly as well. – Michael J. Gray Sep 29 '12 at 23:42
Interestingly enough now. This problem is not present on the machines which are wired into the router, only machines wirelessly connected. Perhaps the wireless switch is behaving differently than the wired one? – Michael J. Gray Sep 30 '12 at 0:01
up vote 1 down vote accepted

Looks indeed like something is filtering wireless access. Can you verify that by changing your laptop from wireless to a wired connection? Run nmap in both cases (wireless as well as wired)

nmap -sT -sU -sV -Pn --traceroute -p U:53,T:53 NAMESERVER_IP

and compare the results. If the wireless trace stops at your wireless AP/router, you need to check its configuration.

For further analysis you may need to give more information about your network topology.

share|improve this answer
It was a NAT issue and after fixing it up it started working after the midnight maintenance restart. +1 for suggesting nmap! – Michael J. Gray Oct 10 '12 at 1:27

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.