Why is my DNS servers not updating when connecting to a hotspot?

Question

This is on a Surface Pro running Windows 10. Pro The issue is, when I connect to a hotspot outside my home, the DNS servers do not update. They still show the servers from when I was connected to my home Wi-Fi. This is an issue since the first two servers my DHCP server reports are internal. For some reason, windows doesn't pick up more than the first two.

I don't have anything hard-coded. The adapter properties is set to get info from the server, basically the default settings.

I can force them to change using the netsh commands. I just don't see why they don't update when I connect to a new AP. Did a hidden flag get set somehow?

Is there a way to check logs or debug this issue?

Please don't suggest hard-coding public DNS servers. I want this to work as intended.

Thanks

Answer 1

Is the WiFi adaptor configured with both IPv4 and IPv6 protocols? Are both configured to obtain IP addresses and DNS addresses automaticaly?

Did the adaptor get a new IP address when it connected to the WiFi hotspot?

Does running ipconfig /renew or ipconfig /renew6 change anything?

Do you have the problem with all hotspots, or just one?

This isn't a PowerShell problem. Why apply that tag to your question?

Answer 2

Hello

Please ensure that the DHCP client service is running. You can open the service management window by running the services.msc command, then look for the DHCP Client service and confirm that its status is Running.

Sometimes, outdated network drivers can cause connectivity problems. You can try to update the network adapter driver to the latest version.

Answer 3

Hello,

Please ensure that the DHCP client service is running. You can open the service management window by running the services.msc command, then look for the DHCP Client service and confirm that its status is Running.

Sometimes, outdated network drivers can cause connectivity problems. You can try to update the network adapter driver to the latest version.

Answer 4

On the off-chance that there's something "stuck" in the registry, check the interfaces beneath this key (they're the UUID if the interface). You'll find a "NameServer" value in there. If you've ever manually set a DNS server for the interface it may not have been cleared

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces

Check the WiFi adapter. Is it set to register the IP address in DNS? I don't think the DHCP host will provide a new DNS server if the client doesn't supply its host name.

If all else fails try removing the adapter and reinstalling it.

If you're really into this, you can grab a packet capture and filter on the DHCP port to see what's being sent by the client to the server and what the server is sending to the client.

Answer 5

I think I “solved” the issue. Unfortunately, I didn't check the registry like Rich mentioned, I wish I would have. Instead, I went with the nuke option. I didn't know windows has a network reset option now. I ran that and it appears to be working again(only tested with my other AP, which didn't work before). Of course, this wipes out all your settings and you will have to log back into all APs again. Thanks for all the suggestions.