Information Technology Reference
In-Depth Information
*** Server can't find Name_or_IP_
address_queried_for
:
Server failed
The DNS server is running, but it is not
working properly. For example, it might
include a corrupted packet, or the zone in
which you are querying for a record might
be paused. However, this message can also
be returned if the client queries for a host
in a domain for which the DNS server is not
authoritative. You will also receive the error
if the DNS server cannot contact its root
servers, it is not connected to the Internet,
or it has no root hints.
In Exercise 2.6, you'll get some hands-on practice with the
nslookup
tool. You can run
this exercise from Windows 7, Windows 8, and Windows Server 2012 R2.
exerCiSe 2.6
using the
nslookup
Command
1.
Click the Start button and in the Search Programs And Files box (above the Start but-
ton), type
Cmd
. Then hit Enter.
2.
Type
nslookup
and press the Enter key. (For the rest of the exercise, use the Enter key to
terminate each command.)
3.
4.
indicates that it can't find the address and times out. This is normal behavior.
5.
Type
exit
at the prompt. Type
exit
again to leave the command prompt.
Using
DNSLint
Microsoft Windows Server 2012 R2 DNS can use the
DNSLint
command-line utility to
help diagnose some common DNS name-resolution issues and to help diagnose potential
problems of incorrect delegation. You need to download
DNSLint
from the Microsoft
Download Center.
DNSLint
uses three main functions to verify DNS records and to generate a report
in HTML:
dnslint/d
This function helps diagnose the reasons for “lame delegation” and other
related DNS problems.
dnslint/ql
This function helps verify a user-defined set of DNS records on multiple DNS
servers.
dnslint/ad
This function helps verify DNS records pertaining to Active Directory
replication.
Search WWH ::
Custom Search