I'm trying to set up my Windows machine so that when both WiFi and Ethernet are connected, it prioritizes the Ethernet connection for DNS queries. Right now, my WiFi is set to use Google's DNS while my Ethernet is connected to an internal DNS server. When I try to resolve internal resources, I notice a significant delay — about 5 seconds — when WiFi is enabled because it seems to be trying to resolve through WiFi first before switching to Ethernet. Is there any way to force Windows to use the Ethernet DNS settings first?
5 Answers
If you don’t really need both connections active, consider disabling one of them. My workplace has strict policies about this, and it simplifies things.
You might want to consider using Group Policy to disable WiFi when the Ethernet connection is active. This way, your machine will focus solely on the Ethernet network, which should speed up DNS resolution for internal resources.
A more straightforward solution could be configuring your WiFi to provide the internal DNS settings instead. That way, you eliminate the delay entirely while still keeping your WiFi enabled.
It sounds like your network priorities are a bit off. You can adjust these settings to ensure the right order. Here’s a handy link on how to change network adapter connection priorities in Windows 10.
It's likely that your Ethernet should take priority over WiFi due to the default interface metrics in Windows. You can check this by running `nslookup` in the command prompt. If you're having issues, you might want to adjust the interface metrics in the network settings in Control Panel.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures