Mar 13 2020 02:11 AM
Mar 13 2020 02:11 AM
I have a Windows Server 2019 VM (HyperV) where I setup my first DC. I also setup DNS and DHCP on the server. After deploying these, the yellow warning icon appeared on the network icon in the bottom right corner, and it says "No internet access". Indeed, Internet access seems to be working normally. The only issue is the DNS sometimes unable to resolve certain random domains. It seems that unbinding IPv6 from the NIC almost solved this issue, but the warning icon and the No Internet message remains.
I tried the troubleshooting tool. It is unable to diagnose the issue, and suggests a network reset. I did it twice, but it did not change anything.
I took a dump of the network packets when the diagnostic tool is run, but I see nothing unusual. It finally connects to http://www.microsoft.com:80/ which I think is the normal way to determine if Internet is available. The server responds 200 Ok and some codes.
I don't know where to look further.
My ipconfig /all:
Windows IP Configuration
Host Name . . . . . . . . . . . . : SrvApp19
Primary Dns Suffix . . . . . . . : psw.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : psw.local
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
Physical Address. . . . . . . . . : 00-15-5D-00-78-03
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.112(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.254
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
I attach one of the diagnostic reports.
Thank to anyone who can help.
Mar 24 2020 01:03 AM
Don't unbind IPv6 :) DNS listener binding does use IPv6 too.
If it's on boot up, check the Event Log for Event ID 4013 - The DNS server is waiting for Active Directory Domain Services...
Normal if you only have the 1 DC and the VM completes the boot process before the services are ready to start. DNS usually waits until AD is complete. You could always spin up 2nd DC with DNS and point to that and see.
Jun 25 2020 09:37 AM - edited Jun 25 2020 09:43 AM
Same problem here and seen a couple of times already. I'm just testing a W2019 deployment in VMware Workstation. Brought up W2019 server, added DNS, DHCP and promoted to DC. Internet is clearly working as can browse BBC website. DNS settings on the DC look correct - forwarding to the router and using 127.0.0.1 for it's own settings. Also deployed a W10 DC using DHCP and added to domain. It's fine, i.e. not reporting "No internet"
Jun 25 2020 09:44 AM
Jun 25 2020 01:36 PM - edited Jun 25 2020 01:38 PM
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 22.214.171.124 (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.
Jun 25 2020 03:56 PM - edited Jun 25 2020 03:59 PM
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.
Jun 26 2020 04:07 AM
Jun 26 2020 04:10 AM
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.
Jun 26 2020 06:12 AM
google DNS knows nothing of the internal domain and cannot be used for DNS on server's connection properties. Always use the server's own static ip address plus loopback and no others such as router or public DNS
Sep 20 2020 08:09 AM
Sep 20 2020 08:15 AM
>google DNS knows nothing of the internal domain and cannot be used for DNS on server's connection properties
I'm talking about the forwarders above and Google DNS servers are as good as any others in resolving *external* requests.
I'd suggest starting your own thread as opposed to hijacking another. Makes things easier to follow.
Nov 23 2020 05:45 AM
I found that my member server 2019 was having this issue, and it's because the router is giving out IPv6 addresses but there is no internet access on IPv6. The solution was to disable IPv6 on the network adapter on the server
Apr 13 2021 11:41 AM
@Luigi_Iottitry restarting the Network Location Awareness service and allow it to restart the Network List service automatically. If it solves the warning then it's because the Network Location Awareness service is starting before DNS. You can fix this by creating a dependency using the following command from an elevated command prompt:
sc config nlasvc depend=DNS
Oct 04 2021 09:00 AM
1. Press Windows + R keys.
2. Type regedit, click OK.
3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet.
4. Make sure following values exist in right pane of Internet:
5. Restart Network Location Awareness service
Referenced from: Arash.Dargahi
On domain controllers using 127.0.0.1 as their primary DNS, run the following:
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\Windows\NetworkConnectivityStatusIndicator" /v UseGlobalDNS /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\MICROSOFT\Windows\NetworkConnectivityStatusIndicator" /v NoActiveProbe /t REG_DWORD /d 0 /f