<div>
<a href="http://searchwindowsserver.techtarget.com/video/Generating-a-DNS-health-check-in-Windows" rel="ugc">http://searchwindowsserver.techtarget.com/video/Generating-a-DNS-health-check-in-Windows</a><br />
<br />
<a href="http://social.technet.microsoft.com/Forums/en-US/dbfba096-5544-4f3d-8859-ae405c18d489/ad-check-health" rel="ugc nofollow">http://social.technet.microsoft.com/Forums/en-US/dbfba096-5544-4f3d-8859-ae405c18d489/ad-check-health</a><br />
<br />
run the dcdiag for the health check first.
</div>


http://searchwindowsserver.techtarget.com/video/Generating-a-DNS-health-check-in-Windows [http://searchwindowsserver.techtarget.com/video/Generating-a-DNS-health-check-in-Windows]

http://social.technet.microsoft.com/Forums/en-US/dbfba096-5544-4f3d-8859-ae405c18d489/ad-check-health [http://social.technet.microsoft.com/Forums/en-US/dbfba096-5544-4f3d-8859-ae405c18d489/ad-check-health]

run the dcdiag for the health check first.

<div>
<div class="content wysiwyg-content">
We have a Windows 2008r2 environment with several offices joined together via MPLS. We recentlly moved the office and in the process added an extra Domain Controller and several new users to the location. I have had some complaints that an otherwise normally functioning printer is printing very slow. In trouble shooting, I realized that the new print server is also the new DC that we added. I work in a different location but I tried to RDP to the DC/Print server from our locaiton and it would not connect. I tried to PING the FQDN and got a response &quot;PING REQUEST COULD NOT FIND HOST&quot;. If I do a PING -a 192.168.5.x, I get a normal reply with the proper FQDN. Some name resolution is happening, but not a direct PING of the FQDN. If I RDP to the other DC in that office, on the same subnet, I can PING and connect to the new DC/Print server fine. I know that is probably related to DNS. Any advice on trouble shooting is welcome
</div>
</div>


We have a Windows 2008r2 environment with several offices joined together via MPLS. We recentlly moved the office and in the process added an extra Domain Controller and several new users to the location. I have had some complaints that an otherwise normally functioning printer is printing very slow. In trouble shooting, I realized that the new print server is also the new DC that we added. I work in a different location but I tried to RDP to the DC/Print server from our locaiton and it would not connect. I tried to PING the FQDN and got a response "PING REQUEST COULD NOT FIND HOST". If I do a PING -a 192.168.5.x, I get a normal reply with the proper FQDN. Some name resolution is happening, but not a direct PING of the FQDN. If I RDP to the other DC in that office, on the same subnet, I can PING and connect to the new DC/Print server fine. I know that is probably related to DNS. Any advice on trouble shooting is welcome

new domain controller seems to not be resolving properly in DNS Windows 2008r2

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.