none
Windows Server 2012 R2 DNS Errors - Missing _msdcs files RRS feed

  • Question

  • Good Afternoon, I have a Windows Server 2012 R2 Datacenter server that has been running Active Directory, DNS, and DHCP. Under the DNS Forward Lookup zones _msdcs it is missing almost all files. It does not have any "folders" underneath it or any ldap files. Joining new computers to the domain has gotten progressively worse and even when joined they will eventually no longer be joined and get errors. I have tried so many things to resolve this including the netlogon stop, start. I have tried to delete the _msdcs folder and get it to rebuilt with commands. I am beyond frustrated at this point. I am debating on moving everyone over to a brand new server that is not part of this domain but this will be hours of work to create new accounts, move files etc. Has anyone seen these errors before and have a fix? I have included the results of my DCDIAG /test:DNS. I did remove any Domain/DNS identifying information.

    I have made sure under IP4 that the DNS box is checked there also. Any advice or help would be appreciated!

    Directory Server Diagnosis


    Performing initial setup:

       Trying to find home server...

       Home Server = 

       * Identified AD Forest. 
       Done gathering initial info.


    Doing initial required tests

       
       Testing server: Default-First-Site\

          Starting test: Connectivity

             The host

             60a31e2d-dd6c-4cf4-8ac8-27dc47cd7dc2._msdcs.

             could not be resolved to an IP address. Check the DNS server, DHCP,

             server name, etc.

             Got error while checking LDAP and RPC connectivity. Please check your

             firewall settings.

             ......................... OHCHS failed test Connectivity



    Doing primary tests

       
       Testing server: Default-First-Site\

       
          Starting test: DNS

             

             DNS Tests are running and not hung. Please wait a few minutes...

             ......................... OHCHS passed test DNS

       
       Running partition tests on : ForestDnsZones

       
       Running partition tests on : DomainDnsZones

       
       Running partition tests on : Schema

       
       Running partition tests on : Configuration

       
       Running partition tests on : 

       
       Running enterprise tests on : 

          Starting test: DNS

             Test results for domain controllers:

                
                DC: 

                Domain: 

                

                      
                   TEST: Basic (Basc)
                      Error: No LDAP connectivity
                      Warning: adapter

                      [00000012] Intel(R) I350 Gigabit Network Connection has

                      invalid DNS server: 
                      Error: all DNS servers are invalid

                      No host records (A or AAAA) were found for this DC

                      Warning: The Active Directory zone on this DC/DNS server was

                      not found (probably a misconfiguration)
                      
                   TEST: Dynamic update (Dyn)
                      Warning: Failed to add the test record dcdiag-test-record in zone 
                   
                TEST: Records registration (RReg)
                   Error: Record registrations cannot be found for all the network

                   adapters

             
             Summary of test results for DNS servers used by the above domain

             controllers:

             

                DNS server: 

                   1 test failure on this DNS server

                   Name resolution is not functional. _ldap._tcp. failed on the DNS server 
                   
             Summary of DNS test results:

             
                                                Auth Basc Forw Del  Dyn  RReg Ext
                _________________________________________________________________
                Domain: 

                   OHCHS                        PASS FAIL PASS n/a  WARN FAIL n/a  
             
             .........................  failed test

             DNS

    Monday, August 13, 2018 7:54 PM

All replies

  • Hi,

    Thanks for your question.

    How did you recreate the _msdcs DNS zone?

    Please refer to the steps in the link below:

    https://www.dell.com/support/article/sg/en/sgdhs1/sln155826/how-to-delete-and-recreate-the-_msdcs-dns-zone-on-a-windows-dns-server?lang=en  

    Best regards,

    Travis


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

    Tuesday, August 14, 2018 6:27 AM
    Moderator
  • That is the document I followed to try to recreate the zone. Thank you though! I really don't know where to go from here.
    Tuesday, August 14, 2018 12:12 PM
  • Hi,

    Thanks for you reply.

    From your test results, I think there is a problem with your DC's DNS address configuration.

    Use the command ipconfig /all to check the DNS address of NIC properties and other configuration. 

    Best regards,

    Travis



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

    Wednesday, August 15, 2018 9:46 AM
    Moderator
  • Hi,

    Was your issue resolved?

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Travis


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

    Friday, August 17, 2018 5:49 AM
    Moderator
  • I know have most of it working correctly! Thank you! The only error I am getting now is on the Network connection "All DNS Servers are invalid. WARNING: The Active Directory zone on this DC/DNS Server was not found. 

    Failed to add the test record dcdiag-test-record in the zone....

    1 test failure on this DNS Server - Name resolution is not function. _ldaps._tcp. Failed on the DNS Server. 

    Otherwise the first part of the test where it was failing before it now passing and everything else looks good. The things listed above are the only bugs left......

    Monday, August 20, 2018 7:36 PM
  • Hi,

    Thanks for your reply.

    Please configure preferred DNS server with 127.0.0.1 on your DC server.

    Then recreate the _msdcs DNS zone again.

    Best regards,

    Travis


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

    Tuesday, August 21, 2018 10:01 AM
    Moderator
  • Hi,

    Was your issue resolved?

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Travis


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

    Thursday, August 23, 2018 6:49 AM
    Moderator
  • Hi,

    Thanks for your reply.

    Please configure preferred DNS server with 127.0.0.1 on your DC server.

    Then recreate the _msdcs DNS zone again.

    Best regards,

    Travis


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

    If my DC is also my DNS server should I change it to the 127.0.0.1.

    We currently have the DNS set for the IP on that box.

    Monday, October 1, 2018 2:05 PM