Hello Garima Das,
Thank you for posting in Q&A forum.
Error 58 in the context of Active Directory replication usually indicates a network-related issue, often tied to name resolution problems. Given that the DNS zone name and domain name are different, it's likely that the Domain Controllers (DCs) cannot resolve each other properly, which disrupts replication.
Here's a step-by-step approach to troubleshoot this issue:
1.Verify DNS Settings on Each DC:
Check DNS Client Settings: Ensure that each DC is pointing to the correct DNS server(s) where the zone for the domain is hosted. Use ipconfig /all
to verify DNS settings.
Check DNS Zone: Open DNS Manager. Ensure that the correct zones exist and that all necessary records (SRV, A, NS) are present for each DC.
2.Add Missing DNS Records if Necessary:
SRV Records: Open DNS Manager.
Expand the zone for your domain. Look for _msdcs.<domain>
, _sites
, _tcp
, and _udp
folders. These should contain records for each DC. If they are missing, consider restarting the Netlogon service (net stop netlogon
and net start netlogon
) on each DC to force registration of the SRV records.
A Records: Ensure there are A
records for each DC in the DNS zone. Manually add these records if they are missing.
3.Verify Zone Name and Domain Name: Make sure that the DNS zone name matches the newly renamed domain.
If the zone name is incorrect, you may need to create a new zone with the correct name and add all necessary records.
4.Check Network Connectivity:
Ping Test: Ping each DC from every other DC to check basic network connectivity. Use both IP address and hostname for the test.
Firewall Settings: Ensure that firewalls on each DC and in between allow traffic on necessary ports (e.g., TCP/UDP 53 for DNS, TCP 135 for RPC, etc.).
5.Check and Flush DNS Cache:
On Each DC: Run ipconfig /flushdns
to clear the DNS cache. Run ipconfig /registerdns
to register the DNS records.
6.Force Replication:
Repadmin Commands: Run repadmin /syncall /AdeP
to attempt a force replication.
Check replication status using repadmin /replsum
to see if errors persist.
7.Check Event Logs:
DC Event Logs: Open Event Viewer and check the Directory Services, DNS Server, and System logs for any errors or warnings related to replication and DNS.
Final Steps:
Review Documentation: Verify your documentation to ensure all steps in the domain rename process were followed correctly.
Restart DCs (if necessary): Sometimes a restart of the Domain Controllers may help in re-establishing proper communication and registration of DNS records.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Best Regards,
Daisy Zhou
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.