<div>
Are you pointing the DC at itself via its real IP address or its Loopback address?
</div>


Are you pointing the DC at itself via its real IP address or its Loopback address?

<div>
I figured it out -- I did an ipconfig and found that there were DNS suffixes in there that don't exist, so it seems like it was timing out with those before resolving locally.<br />
Thanks for the help.
</div>


I figured it out -- I did an ipconfig and found that there were DNS suffixes in there that don't exist, so it seems like it was timing out with those before resolving locally.
Thanks for the help.

<div>
<div class="content wysiwyg-content">
I have a DC running Server 2003, SP2 with the Active Directory and DNS role. &nbsp;When I ping itself by name, the response is instant, but when I ping another server/machine on the network, it takes like 5-8 seconds to resolve the name and then the ping is successful.<br />
If I ping from any other machine on the network, the response is instant, just not on my DC/DNS server.<br />
<br />
Any thoughts?
</div>
</div>


I have a DC running Server 2003, SP2 with the Active Directory and DNS role.  When I ping itself by name, the response is instant, but when I ping another server/machine on the network, it takes like 5-8 seconds to resolve the name and then the ping is successful.
If I ping from any other machine on the network, the response is instant, just not on my DC/DNS server.

Any thoughts?

DNS slow name resolution

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).