none
AD Replication dns zone replication error

    Question

  • Hi Experts,

    Recently, I have removed GRNL WRAP error from DC (2k8) and added additional domain controller (2k16) and have transferred roles into newer server. Replication has successfully created all DNS zones, however when I hit "repadmin /syncall" I can see only default DNS zones getting replicated.  Secondly, users are taking old DC as primary dns server even if I am keeping the newer dns first.

      

    Thursday, February 2, 2017 10:52 AM

All replies

  • Hi,
    >> only default DNS zones getting replicated
    Did you get any detail error message or event logs? And please make sure that AD replication between DCs has been fully completed, you could run repadmin /showreps from the newly promoted DC to see details and please wait for some time and then see if the DNS zones are replicated, please see a similar thread as below for more reference: https://social.technet.microsoft.com/Forums/sharepoint/en-US/ff629584-7e23-43fe-a998-a04800a54939/dns-not-replicating-to-new-dc?forum=winserverDS
    >> Secondly, users are taking old DC as primary dns server
    Please make sure that the clients point to windows server 2016 DC’s IP address as primary DNS server, then run "ipconfig /flushdns & ipconfig /registerdns" and restart DNS and NETLOGON service on each DC.
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, February 3, 2017 3:26 AM
    Moderator
  • Hi

     Inaddtion you should check DNS Functionality&health;

    run "dcdiag /test:dns /v /s: <DCName> /DnsBasic f:/dcdiagreport.txt" ... Also check the article for details;

    https://technet.microsoft.com/en-us/library/dd728017(v=ws.10).aspx

    Troubleshooting zone problems

    https://technet.microsoft.com/en-us/library/cc731210%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396

    Secondly, users are taking old DC as primary dns server even if I am keeping the newer dns first >>> And if you have DHCP,just configure new server 2016 DC as primary as Dns..


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Friday, February 3, 2017 7:09 AM
  • Hi,

    Just checking in to see if the information provided was helpful. And if the replies as above are helpful, we would appreciate you to mark them as answers, please let us know if you would like further assistance.

    Best Regards,

    Wendy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, February 10, 2017 8:36 AM
    Moderator