Share via

DNS Issues – AD Domain, internal only

Jorg menting 21 Reputation points
2022-02-20T10:57:35.98+00:00

So, I have a weird DNS issue in one of my office buildings. It is not a client issue, as this is happening to all machines in the building.

We can ping on IP internally, but not on name. NSLOOKUP works fine and gives the correct results. Internal ping on host name gives straight away the error “Ping request could not find the host”. This failure comes on both host name and FQDN.

We can however ping external sources, like www.google.com, without issues.
Now, the weird thing is, ping on name fails on all machines, EXCEPT for the virtual machines and our 2 Hyper-v physical hosts. They all work fine. Our Meraki switches can ping the FQDN, but not the host name.
If I connect with Direct Access to our gateway server, then again we can ping internal resources.

In IPCONFIG /ALL, it shows the Connection-Specifix DNS Suffix correctly, but if you hoover over the LAN connection in Windows 10, it cant Identify the network.
Our DNS servers are also our DC’s and 1 of them does DHCP, in IPCONFIG, the correct settings are being applied.

I am currently at a loss, any ideas what is causing DNS/ AD network Identification to fail?

What have we tried.

  1. We didnt apply any patches to the DCs during the weekend (it failed monday morning), but we did a restore of both DCs from a few days before, this didnt resolve the issue.
  2. Did you turn it off and on again, yes we did.
  3. We shutdown the entire network, including all switches and Fortigate firewalls. We then brought online only the SAN, both Hyper-V hosts and the DC's (both VMs). And the 2 meraki switches in the server room. I then attached 1 laptop to the same switch in the server room, still cant ping internally on name.
  4. I made a brand new VM (windows 10), this one CAN ping on host name
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
Accepted answer
  1. ABDUL KARIIMU GGUBYA 166 Reputation points
    2022-02-20T11:36:35.943+00:00

    Hello @Jorg menting

    Kindly remove the machines from the domain and rejoin them again. Then you will be able to ping by hostname. If that works kindly let me know

    Reason: You restored to the old Active Directory database which in most cases makes the joined clients to loose the domain trust or not find the domain controllers.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-02-20T14:51:01.453+00:00

    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.

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.