browsers(s) dns timeout but CMD environment (ping) works

Question

3 browsers (Edge, Chrome & Firefox) DNS name resolution fails* but win10 CMD box still resolves names and pings

• happens after a second workstation boots, account logged in, rebooting the router clears the problem

DNS service on the LAN by AD DNS

Answer 1

All looks Ok to me, the only issue (and not a showstopper) is each domain controller should have (at minimum) own static ip address and loopback 127.0.0.1 listed for DNS so I'd add DCs own static address, then do ipconfig /flushdns, ipconfig /registerdns, then restart the netlogon service. On all three.

3 browsers (Edge, Chrome & Firefox) DNS name resolution fails* but win10 CMD box still resolves names and pings. rebooting the router clears the problem

This is a little vague but I think that's the right direction. I'd try asking the router manufacturer or the ISP for further assistance.

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

Answer 2

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on any domain controller)
ipconfig /all > C:\%computername%.txt (run on EVERY domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)

Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)

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

Answer 3

here it is:

https://1drv.ms/f/s!AobJcD-Mue5hzgpmXOPR6R6TEovg?e=ggcq1j