Strange DNS Issues - Trying to add a Windows 11 Desktop to a domain

Anonymous
2024-08-19T17:40:38+00:00

Good Afternoon,

So I got a CyberGeek mini PC for use as a jump box or quick testing box. I have a small network at the house... Where this issue is. My Network is:

  1. Meraki MS2200 24 Switch
  2. Meraki MX64 Firewall
  3. UCS C200 M2 Rack Mount server
  4. Buffalo NAS (5TB)

On the server I have a VM that is my domain controller (my domain is: slappy.home) and it is running the DNS Server. On the DNS Server I have added the A HOST record for the new device. I also have the DNS prescribed in the Adapter settings (IPV4). I can ping every device and VM in the network from the new device... IF I just used the device name (new system is called TEXSYSWIN1101 and I have a laptop called TEXLNX001 and I can ping those.

HOWEVER, if I try to add the new device to the domain I get the vile message that the "DNS Name does not exist"... yet I can ping the server (homegrown1) by name... if I try to ping the FQDN (homegrown1.slappy.home) I get a external of BS IP of 144.128.36.250.. When I trace route that IP of course I get the * * * * lines just after my ATT router... then at the very end I get that IP (no name) stating it completed successfully.

I cannot figure this one out. Just weird. I know it has to do with the FQDN not responding correctly, but how to resolve that is the question. I have flushed the DNS several times, rebooted a ton, the basics... Just curious if anyone ever had a similar situation and if so how did you rectify it? Just curious!

Windows for business | Windows Client for IT Pros | Networking | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} vote

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-08-20T12:53:52+00:00

    Hello,

    This error means that your computer cannot find the Active Directory domain controller. I recommend that you open the Network Sharing Center, select "Internet Protocol Version 4 TCP/IPv4", and then open "Properties". Point the client's preferred DNS server address to the domain controller's IP address.

    Best Regards

    Zunhui

    0 comments No comments
  2. Anonymous
    2024-08-20T13:03:19+00:00

    That is already set. The basics are completed. IPV4 DNS set in the adapter configuration, I also created an entry in the hosts file for the domain controller. Like I stated... I can get a positive ping when I run "ping servername" it returns correctly. if I try to ping the FQDN "ping servname.slappy.home" I get an IP address of 144.234.36.250. There is something else weird going on. I need a deeper dive I fear.

    0 comments No comments
  3. Anonymous
    2024-08-23T09:25:38+00:00

    Thank you for your reply. I suggest you open cmd as an administrator and run the following command to reset the client network and then re-join the domain.

    ipconfig /release

    ipconfig /renew

    ipconfig /flushdns

    ipconfig /registerdns

    resetting IP netsh int

    Netsh Winsock Reset

    Best Regards

    Zunhui

    0 comments No comments