I can not see DNS records inside DNS zones in secondary domain controller

Federico Coppola 1,181 Reputation points
2021-06-17T19:32:11.593+00:00

Hi all,
I have two Domain Controller inside company.
Both of them are Windows 2016 DataCenter and they are installed in English Language.

Today I noted this issue:

On the first domain controller, inside DNS I can see all records inside the DNS zones.
On the second domain controller, inside DNS I see just DNS zones but inside domain zone there aren't DNS record, there are just the NameServer record!

After that I tried to the first domain controller, using DNS console, to connect to the second domain controller.
In this case I can see all DNS zones and records properly

What can I do?

Thanks
Federico

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,511 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,113 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,039 questions
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2021-06-19T12:18:22.957+00:00

    There seems to be some sort of corruption on this server. As a work-around it sounds like you can just use the newly created MSC but in my opinion I'd replace that domain controller ASAP.

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new one for replacement, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

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

    0 comments No comments

17 additional answers

Sort by: Most helpful
  1. Federico Coppola 1,181 Reputation points
    2021-06-19T13:50:09.847+00:00

    Dear @Anonymous ,
    Thanks for this suggestion!

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations

    Yes you are right, you tought me new command to check health. Thanks!

    There seems to be some sort of corruption on this server. As a work-around it sounds like you can just use the newly created MSC but in my opinion I'd replace that domain controller ASAP.

    Yes it is the best solution.

    Thanks
    Federico


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.