Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Mike Aucoin

_msdcs missing 2012R2 to 2022 migration

Hello,

While wrapping up a migration (step 18.2) from 2012R2 to Server 2022 I do not see _msdcs within DNS. See the attached screenshot. Any help is greatly appreciated.

-Mike

 

Attached Files
asked10/04/2023 00:00
304 views
Add Comment
Last Activity 10/19/2023 03:49

1 Answer(s)

  • Mariette Knap

    If this zone is not functioning properly, if the records are missing in the zone, domain members may not be able to contact the Domain Controller and thus may not be able to access users/device authentication in the domain.

    If all other steps failed to fix the problem, you need to delete and recreate the _msdcs zone zone.

    Before deleting the zone, backup the existing Active directory data ( copy in the contents of the %windir%\System32\dns folder and backup the system state of a DC which is in DNS server)

    Follow the following steps to delete and recreate the _msdcs zone:

    1. Open the DNS console (Administrative Tools-> DNS or run dnsmgmt.msc). Right-click on the _msdcs zone folder and Delete.
    2. Right-click Forward Lookup Zones in and select New Zone.
    3. Use that wizard to create the new zone.
    4. Name new zone _msdcs.<domain>, The domain should be in full DNS name of your AD domain. Example, if your domain is domain.local, the new  zone name should be _msdcs.domain.local
    5. Right-click your server and select All Tasks -> Restart to restart the DNS service.
    6. Open a CMD and run the followings:
      ipconfig /flushdns
      ipconfig /registerdns
      net stop netlogon
      net start netlogon
    7. Wait a sometime and refresh the DNS console. It will take sometime to populate the new _msdcs zone.
       

    If you have multiple Domain Controllers in the domain, run step 5 again on each one to register and refresh the DNS server.

    answered 10/11/2023 08:13
    Add Comment
    Mike Aucoin

    Hello,

    I need to provide further clarification to my original post. The _msdcs.domain.local zone exists, but the _msdcs NS record within domain.local zone does not exist. It is the only missing record on the new server.

    The _msdcs NS record on the old server within the domain.local zone was pointing to an old server that hasn't been on the network since the old server was implemented, so I don't see it serving any purpose. 

    Do I need this NS record? If so, is there a way to create it without rebuilding the zone? 

    See attached screenshot for details. 

    Thank you very much.

    Attached Files
    Reply
    replied 10/13/2023 14:05
Add an Answer