Article Summary: This article provides information on troubleshooting Active Directory and DNS replication.
1. Find the Flexible Single Master Operations (FSMO) role holders
2. Narrow down the problem
3. Visually inspect DNS
4. Visually inspect sites and services
5. Use event IDs to narrow troubleshooting
6. Other tools available
Begin by finding the domain controllers (DCs) in the organization. Focus on the health of your forest root and work your way out.
Find the FSMO role holders by opening an elevated command prompt and typing:
netdom query fsmo
This will return a list of the DCs holding each role:
To narrow down the problem, it is important to be systematic. Use the following tools to test various DCs, their connection to the root domain or role holder, their ability to resolve names to IP addresses, open ports, and replication results.
Try to pinpoint a specific server that does not communicate and determine if the source or destination server is the cause. Event logs and replication results are ways to gain additional information.
Open the DNS console by going to Start -> Administrative Tools -> DNS. Click the DNS server in the left pane.
Review the forward lookup zones and all other zones related to the forest and domain partitions.
Guidance is available from Microsoft TechNet using this link: Troubleshooting DNS
Some things to look for in the DNS console include:
You can find more information about the DNS infrastructure from the Microsoft TechNet DNS Server page.
The Active Directory Sites and Services console contains several items that may help troubleshoot replication failures. Inspect and open every folder and look for the following:
AD-related errors can be found in the Event Viewer console.
The fastest way to get there is to go to Start -> Run and type eventvwr.msc.
Relevant event logs include the System, DNS, Directory Service, and File Replication Service log.
Use the following articles to help determine the next steps, based on errors found in the logs:
Nltest is a useful command-line tool that can return many kinds of information about an AD domain.
The metadata cleanup process is used to remove AD references to DCs that were taken offline without being properly demoted.
Lingering objects are AD objects that have been deleted from one DC but remain on another due to a replication failure.
Removing these objects is a necessary step in restoring proper replication.
Article ID: SLN156253
Last Date Modified: 09/23/2014 02:26 PM