Major DNS issues with Windows Client joining New Domain Controller

Taylor507 1 Reputation point

I recently set up an AD DC on Windows Server 2019 VM and am in the process of adding one Windows 10 vm client to the DC. (I am working in vmware workstation pro and working with a NAT adapter option).

However, I keep running into issues with the Windows 10 vm client--as soon as I set my static ip address it disconnects from the internet.

For reference, I first used DHCP and wrote down the ip address, mask, and default gateway assigned for the client. Then I entered excatly that to set the static IP address, and used the ip address of my server as the DNS server. I believe this is the correct way to configure a static address on a client, but as soon as I hit "OK" it disconnect from the internet.

When I try to join the client to the server, I get the error message "An AD DC Domain Controller for the domain xyz.local cannot be contacted. Ensure that the domain name is typed correctly".

I have a feeling it's related to the issue with the internet not connecting when I set the static ip address. I tried pinging the domain name from command prompt, but I get the error "Ping request could not find host xyz.local. Please check the name and try again".

It seems there is absolutely no connection at all. Nslookup also doesn't work and I can't look up the domain name and simply times out after several attempts.

I hope I can get some help soon as I'm falling behind on my projects because of this:(

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
9,540 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
4,352 questions
Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,054 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Dave Patrick 354.1K Reputation points MVP

    I'd check that the domain controller and all members have the static address of DC listed for DNS on connection properties and no others such as router or public DNS.

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

  2. Dave Patrick 354.1K Reputation points MVP

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\dc3.txt
    ipconfig /all > C:\problemworkstation.txt

    then put unzipped text files up on OneDrive and share a link.