Share via

DNS Resolving on Client Computers but failing on DC

Jessica 341 Reputation points
2021-04-05T17:08:12.283+00:00

My Domain Controller is failing to resolve any DNS records:
![84477-image.png]2

However all the client Machines that are connected to the DC can resolve all the DNS records with no issues:
84513-image.png

I am running a Virtual Switch, VPN and a few other things on the system if this may be any help to solving the issue.
This is really messing up a lot of things as I can't use any RPC features which prevents me from updating policies across the entire network.
84435-image.png

My DNS setup doesn't seem to be incorrect.
84533-image.png

Hopefully someone may have an answer to this issue, if I find a solution to the issue I will post it here.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,491 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,237 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,959 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,562 questions
0 comments
Accepted answer
  1. Dave Patrick 426.2K Reputation points MVP
    2021-04-05T18:11:08.593+00:00

    The simplest solution may be to remove the VPN and routing from the domain controller.

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

8 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Dave Patrick 426.2K Reputation points MVP
    2021-04-05T19:35:48.633+00:00

    For standard edition yes that's correct.

  2. Dave Patrick 426.2K Reputation points MVP
    2021-04-05T19:28:57.343+00:00

    Some general info

    • Each host needs to be licensed.
    • A minimum of 8 core licenses is required for each physical processor and a minimum of 16 core licenses is required for each server.
    • Core licenses are sold in packs of two.
    • Standard Edition provides rights for up to 2 Operating System Environments or Windows Servers containers with Hyper-V isolation when all physical cores in the server are licensed. For each additional 1 or 2 VMs, all the physical cores in the server must be licensed again.
    • DataCenter Edition provides rights for unlimited Operating System Environments or Windows Servers containers with Hyper-V isolation when all physical cores in the server are licensed.

    https://download.microsoft.com/download/7/C/E/7CED6910-C7B2-4196-8C55-208EE0B427E2/Windows_Server_2019_licensing_datasheet_EN_US.pdf

  3. Dave Patrick 426.2K Reputation points MVP
    2021-04-05T19:24:40.497+00:00

    Sounds good, yes stick to using the GUI configuration for now.

  4. Dave Patrick 426.2K Reputation points MVP
    2021-04-05T19:11:44.17+00:00

    Not really, as I already mentioned multi-homing a domain controller will cause unexpected / unreliable results as you have already experienced. Standing up virtual machines using hyper-v manager is fairly simple and straight forward.
    https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/get-started-with-hyper-v-on-windows