Server 2019 DNS cant resolve sites on Windows 10

Niklas Akerö 21 Reputation points
2021-04-19T08:42:09.247+00:00

Hello,

I have a domain with two 2019 AD Servers with DNS activated. Added to a 2008 R2 domain, i still have one 2008 R2 server in domain (to be be retiered) soo the Domain level is 2008 R2.

Some sites on "all browsers" on windows 10 cant be resolved (timed out), i can run the sites on the server.

Info:

Fotwarders are applied on ip v4 and can be resolved.
No ip v6 revers zone activated.
DNS servers DNS points to own and other DNS server.

Regars.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,451 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,021 questions
0 comments
Accepted answer
  1. Dave Patrick 426.1K Reputation points MVP
    2021-04-20T14:25:07.783+00:00

    EHLMDC005 should have own static ip address (192.168.1.5) listed for DNS then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service

    EHLMDC006 should have own static ip address (192.168.1.6) listed for DNS also remove the public DNS (8.8.4.4) then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service

    EHLMDC003 should have own static ip address (192.168.1.3) listed for DNS then do ipconfig /flushdns, ipconfig /registerdns, restart the netlogon service

    Something may be broken with windows time service, needs investigated. There is time skew between servers
    https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/

    " Unable to connect to the NETLOGON share!" Are sysvol / netlogon shares present on all three domain controllers?

    "The DFS Replication service encountered an error communicating with partner EHLMDC006 for replication" I'd check the event logs for more details about this one

    EHLMVP01 DHCP subnet mask seems a little odd 255.0.0.0

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

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2021-04-19T12:53:51.123+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.

  2. Dave Patrick 426.1K Reputation points MVP
    2021-04-19T13:11:34.163+00:00

    Do you want me to run the commands on the DC/DNS?

    Three DC's and problem workstation.

    0 comments
  3. Sunny Qi 10,896 Reputation points Microsoft Vendor
    2021-04-20T08:16:33.517+00:00

    Hi,

    Thanks for posting in Q&A platform.

    My understanding is there are 2 Windows 2019 server with AD DS and DNS roles in your environment. And forwarders have been configured on these 2 DNS servers. The site can be accessed from server 2019 side but cannot be accessed from Windows 10 client side. Please correct if my understanding is wrong. What about the role of windows 2008 R2, is it also a DNS server in the same domain?

    May I know how do we configure the DNS servers on Windows 10 client?

    Kindly share the results of DSPatrick's recommendation for further troubleshooting.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.