Router DNS vs. Windows DNS

Caporegime
Joined
13 May 2003
Posts
34,559
Location
Warwickshire
Hi all

If my router's DNS is set to 8.8.8.4 / 8.8.4.4 (i.e. Google) and my Windows PC is set to 'obtain automatically', what DNS address will actually be used?

What about if my PC is set to use, say, Virgin's DNS servers?

Thanks.
 
Generally your PC will set your routers IP for DNS lookup and then your router will forward it to the ones you have set it too. (Defaulting to virgin's) if you didnt change it.

www.dnsleaktest.com if you want to see what DNS your pc is using.
 
Your router's DHCP server will set the PC's DNS to whatever the router is set to.

If you set them manually on the PC it'll use what you've set.

IPCONFIG will show you what it's set to.
 
You want your PC to use the router's DNS, otherwise it won't be able to see any other local machines.

If your router is set to use 8.8.8.8, then it will look up DNS through that and sent it to your PC.

Ie, if your router IP is 192.168.1.1, that's what your gateway and DNS should be set as on your PC.
 
There are other ways for Workgroup PCs to resolve network names. If you're running a domain then you need DNS, but that isn't the usual home setup.

Or I could be wrong...
 
Curious on this topic too, I've always wondered whether it was best to set DNS via the router's WAN or DHCP server? I've been told DHCP as it uses less CPU cycles on the router...
 
Last edited:
How would you set DNS via WLAN? That makes no sense to me at all.

He means set the dns manually as part of the WAN connection (dont auto connect to ISP's use my own) This way the computers ext just use the router to forward DNS requests to google or open dns or whatever

or set the DHCP server to send the actual ip's of the dns servers to the computers so that it bypasses asking the router.

Way 1) you get to use whatever dns you want however devices just use the router as the DNS and the router forwards it

2) the actual devices have the IP of the dns servers bypassing the router.

ipconfig
192.168.0.1 for option 1 the router forwards it to 8.8.8.8
8.8.8.8 for option 2
 
I don't understand the obsession with Google DNS, your ISPs DNS should be the shortest hop and be reliable.

I set my machines to use my local DNS and that draws from my ISP first followed by Google then open DNS
 
Cheers guys, lots of useful info. That link confirms I'm using Google dns.

I wouldn't call it an obsession, I'm just experimenting as Google.co.uk takes far longer than it should to load for some reason, so I wanted to try Google DNS to rule out that being the issue.

No change, so I guess it's a software problem (only noticed it since upgrading from Windows 7 to Windows 10.
 
He means set the dns manually as part of the WAN connection (dont auto connect to ISP's use my own) This way the computers ext just use the router to forward DNS requests to google or open dns or whatever

or set the DHCP server to send the actual ip's of the dns servers to the computers so that it bypasses asking the router.

Way 1) you get to use whatever dns you want however devices just use the router as the DNS and the router forwards it

2) the actual devices have the IP of the dns servers bypassing the router.

ipconfig
192.168.0.1 for option 1 the router forwards it to 8.8.8.8
8.8.8.8 for option 2

Yes mate, typo I've corrected my post to WAN. :p

Does anyone know if there is any benefit whether the DNS is set in the WAN, DHCP or both? :confused:
 
As a business we always use the ISP DNS as the first two and then Google as the third. Latency is key for business users, if it takes any longer than 2-3 seconds they're on the phone complaining their entire PC is slow because they can't get on Facebook quick enough...
 
As a business we always use the ISP DNS as the first two and then Google as the third. Latency is key for business users, if it takes any longer than 2-3 seconds they're on the phone complaining their entire PC is slow because they can't get on Facebook quick enough...

Router with DNS caching is brilliant for this.
 
Back
Top Bottom