Information Technology Reference
In-Depth Information
5.
In the Advanced TCP/IP Settings dialog box, click the DNS tab and verify that the
following are set correctly:
IP address of one or more DNS servers on your network
The configured DNS suffixes
Whether the host should update its information dynamically with the DNS server
6.
Click OK when you're done.
Using a Command-Line Interface
The following command will confirm that you can connect to a remote host called
www.
mycompany.com
by using its fully qualified domain name (FQDN):
> ping www.mycompany.com
The following command will send a query to the default DNS server configured for the
local computer:
> nslookup www.mycompany.com
The following command will send a query to the DNS server with the IP address of
10.0.0.130
:
> nslookup www.mycompany.com 10.0.0.130
How It Works
As when troubleshooting NetBIOS name resolution, you can confirm whether or not DNS is
functioning correctly on a Windows Server 2003 computer by pinging or otherwise connecting
to a remote host using its fully qualified domain name (FQDN). If the ping is successful, DNS
name resolution is functioning correctly and the issue lies somewhere else: perhaps the file or
service to which you are trying to connect on the remote server is unavailable. If you are unable
to ping the remote computer's DNS name but you
are
able to ping its IP address, you should
begin your troubleshooting steps at DNS name resolution. You may also run into a situation
where DNS is incorrectly configured, where you may be pinging a DNS name that is resolving
to an incorrect IP address. It's important to ensure that both pieces of the puzzle are correct
when troubleshooting using ping.
To troubleshoot the accuracy of DNS records hosted on a local or remote DNS server, you
can use the nslookup and netdiag command-line utilities. Like netsh, nslookup has a number
of subcommands that you can use to customize the information you're looking for, including
querying for a specific type of record (
A
,
CNAME
, or
MX
, for example), and to customize which DNS
servers you are using to perform a query. The netdiag utility from the Windows Support Tools
also includes a DNS component as part of its battery of tests. The
netdiag /test:dns
command
will check whether the DNS cache service is running and whether the local computer's DNS
records are registered correctly on its configured DNS servers. If the local computer is an Active
Directory domain controller, the DNS test will also verify that any DNS entries in the netlogon.dns
file are registered on the DNS server.
