A single domain controller configures the local TCP/IP stack to use itself (127.0.0.1) for DNS resolution. This results in the Network Location Awareness service failing.
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:
"ActiveDnsProbeContent"="8.8.4.4"
"ActiveDnsProbeContentV6"="2001:4860:4860::8844"
"ActiveDnsProbeHost"="dns.google"
"ActiveDnsProbeHostV6"="dns.google"
"ActiveWebProbeHostV6"="www.msftconnecttest.com"
"EnableActiveProbing"="1"
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
References: