My DNS server is not receiving DFS Replication

Question

The DFS Replication service failed to communicate with partner <DC Server> for replication group Domain System Volume. This has been going on for 2 weeks. Utility Server shared drives would be inaccessible intermittently. After flushing the DNS cache and restarting the DNS server,, the DNS server is no longer resolving server names.

Answer 1

I'd check the required ports are open and flowing between them.

https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/config-firewall-for-ad-domains-and-trusts#windows-server-2008-and-later-versions

You can also try a non-authoritative sync

https://learn.microsoft.com/en-us/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization#how-to-perform-a-non-authoritative-synchronization-of-dfsr-replicated-sysvol-replication-like-d2-for-frs

also check the System and DFS Replication event log for more clues.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

The issue you're experiencing with the DFS Replication service and DNS server can have several possible causes. Here are some steps you can take to troubleshoot and resolve the problem:

Check network connectivity: Ensure that there are no network connectivity issues between the servers involved. Verify that the network connections are stable and that there are no firewall rules or network configuration blocking communication.

Verify DNS settings: Double-check the DNS settings on both the Utility Server and the DNS server. Ensure that the DNS server IP address is correctly configured on the Utility Server and that the DNS server itself is properly configured to resolve server names.

1. Flush DNS cache: On the Utility Server, flush the DNS cache by running the following command in an elevated Command Prompt or PowerShell window:

ipconfig /flushdns

Verify DNS server functionality: Restart the DNS server and monitor its status. Check the DNS server logs for any errors or warnings that might indicate issues with DNS resolution. Make sure that the DNS server is running and able to respond to queries.

DNS forwarders: If your DNS server is configured to use DNS forwarders, ensure that the forwarders are correctly configured and operational. Test DNS resolution by querying external domain names to see if they are resolved successfully.

DNS zones and records: Check the DNS server for any misconfigured or missing DNS zones and records. Ensure that the necessary DNS records are present for the servers involved, including A records and possibly SRV records for domain controllers.

Replication configuration: Review the DFS Replication configuration for the replication group "Domain System Volume." Ensure that the partner server <DC Server> is correctly specified and that the replication group settings are properly configured.

Event logs: Examine the event logs on both the Utility Server and the DNS server for any relevant error messages or warnings that could provide further insight into the issue.

Restart servers: As a troubleshooting step, consider restarting both the Utility Server and the DNS server. This can help resolve any temporary issues and ensure a fresh start for the services.

If the problem persists after trying these steps, you may need to involve your network or system administrator for further investigation and assistance.