Home / server / Questions / 445163
Accepted
Vazgen
Asked: 2012-11-04 14:51:15 +0800 CST

Hyper-V Server hvremote.wsf Script - ns lookup for DNS Verification test fails

  • 772

I'm trying to connect my Hyper-V Server to a Windows 8 client for remote management.

I have:

Joined server to WORKGROUP

Enabled Remote Management

Set the server name

Set a static IP

Set the DNS servers to my ISPs DNS Servers (same as default DNS Servers on my Windows 8 remote management client)

Set the correct time zone

Created net user on server (net user /add admin password)

Added user to special Administrators group on server (hvremote /add:admin)

Granted anonymous dcom access on client using hvremote

However, the "ns lookup for DNS verification" fails on both the client and server with the same error:

Server: my.isps.server.name.net

Address: 111.222.333.1

********* my.isps.server.name.net can't find 192.168.1.3: Non-existent domain

Thanks for the help.

domain-name-system

1 Answers

  1. Best Answer

    That's because your ISP DNS servers don't hold DNS records for your internal network. What you need to do is to set up an internal DNS server that your internal hosts will use for DNS name resolution. Once set up you can manually add the relevant host records for your internal hosts or you can configure your internal hosts to dynamically register and update their own DNS records.

    Note that DDNS is the default for Windows DNS clients but in order for it to work in a workgroup you need to configure the hosts with your internal DNS suffix and you need to configure your internal DNS zone to allow secure and non-secure updates.

    There are other variables that could come into play (such as if you create an AD domain and join these computers to the AD domain) but I've intentionally tried to keep my answer as simple as possible.

    • 2