Window Server 2012 R2 Forward DNS Zone xxxxx.local is corrupt

Bonnie Whalon 141 Reputation points
2020-08-14T02:11:57.673+00:00

The server apparently had some type of power strike and when it came up the DNS forward Zone did not load. I tried to refresh, and reload. I stopped the service and restarted it. The domain controller is a guest server on a Windows Hyper-V server. It is the only DC on the network. I can do an reverse NSLookup. There is also a SQL server Quest. All servers are Windows 2012R2. The systems cannot find the SQL server. I'm getting different errors with each workstation. 17611-server-dns.png17584-sql-mj.png

17585-sql-b.png

Thank you for your help.

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,524 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
    2020-08-14T12:48:34.767+00:00

    I'd check the domain controller has own static ip address besides loopback (127.0.0.1) listed for DNS then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service.

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

    0 comments No comments

6 additional answers

Sort by: Most helpful
  1. Bonnie Whalon 141 Reputation points
    2020-08-21T21:39:16.533+00:00

    I needed to call Microsoft. The issue was the Hyper-V had an Active Directory and DNS as well as the Domain Controller had an Active Directory and DNS. The DC section of the Active Directory on the Hyper-V was corrupt. Microsoft rebuilt it and it came back clean.

    I thought this was not an acceptable configuration but the Microsoft Technician said he seen it many times. I'm accepting both your answers because you were on the right track and it helped to pinpoint the issue.

    Thank you for all of your help.

    0 comments No comments

  2. Anonymous
    2020-08-21T21:43:36.447+00:00

    Glad to hear it's sorted. Yes, its always recommended to have at least two domain controllers for high availability and disaster mitigation, but neither should have the hyper-v role installed. Always best to set affinity such that the domain controllers cannot migrate to the same host.

    0 comments No comments

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.