If the preferred server is authoritative for the failed name and it loads the applicable zone, determine whether the zone is missing the appropriate resource records.
No-IP Priority Support is a priority response support channel that is staffed with our friendly and experienced Technical support team.
Priority Support allows you to get the support you need as quickly as possible.
Solution: If the DNS client has basic connectivity to the network, verify that it can contact a preferred (or alternate) DNS server.
To verify whether a client has basic TCP/IP access to the DNS server, first try contacting the preferred DNS server by its IP address by using the ping command.
For example, at the client computer, type ipconfig /all|more if necessary to pause the display so that you can read and note any IP addresses that are listed in DNS servers for the command output.
If no configured DNS servers respond to a direct pinging of their IP address, it indicates that the source of the problem is more likely a network connectivity problem between the client and the DNS servers.
To verify a client IP configuration, use the ipconfig command.
In the command output, verify that the client has a valid IP address, subnet mask, and default gateway for the network where it is attached and being used.
If the client does not have a valid TCP/IP configuration, you can either: For more information, see Managing Clients.
Cause: The client was not able to contact a DNS server because of a network-related or hardware-related failure.
For more information, see Start or Stop a DNS Server.