Forum Discussion
Windows Server 2019 warns No Internet Access after AD, DNS and DHCP setup
I've got a workaround for this. I appears to be something to do with when you have a single DC where the DNS is configured as 127.0.0.1. With a set-up like this, the "No internet" message occurs although it's clear one has perfect internet access.
My workaround is to add the IP address of another DNS server. The upstream router in this example but could equally be 8.8.8.8 (Google DNS):
Once you add that second DNS, the "No internet" message disappears.
In a more normal domain set-up, best practise means you have two domain controllers and DNS servers. In which case, the DC would have DNS settings of 127.0.0.1 (itself) and the IP of the other DNS server.
google DNS knows nothing of your private domain. domain controller should always have at least own static ip address, and loopback (127.0.0.1) listed on connection properties. Never use router or public DNS here. Internet queries are passed on in a top-level down fashion by default to the 13 root hint servers, or optionally any configured forwarders.
- This fault is nothing AFAIK to do with root hints - they are only ever used when the forwarder DNS server fails or is not configured.
It's some flaw in the check for internet access when running on a single domain controller system. When you promote a member to a domain controller and install a DNS server at the same time, it removes the DNS settings against the NIC, uses that for the DNS server forwarder and replaces it with 127.0.0.1. This works perfectly for everything except for whatever test is being carried out for internet connectivity.
Adding the DNS setting on the DC for an upstream DNS server (e.g. router or Google DNS or OpenDNS) and the check starts working.
The DC itself will refer to itself as 127.0.0.1 is checked first and most of the time will work.It might be because it's very common for the forwarded DNS server to fail to resolve if it's picked up the upstream router like this. I'm just going to change the forwarder to Google DNS and remove from the static IP configuration to see if that works as well.
- created account to like this comment 🙂
- Mate I just want to say thank you, from the bottom of my heart. I spent way too many hours on this thing. Adding the alternate DNS server as 8.8.8.8 finally solved it. God bless ya.
