- Thread Author
- #1
I am working with a couple of inhouse computers (Desktop & notebooks) in a LAN behind a router.
In the past I have always setup the router IP 192.168.0.1 as DNS server in the Win 7 LAN settings dialog.
Does that make sense?
Because the router hardware itself does not contain a DNS server (or at least with some very poor caching) he has most of the time forward all DNS request from e.g. my notebook to the outside broadband providers DNS server.
So why not entering directly the broadband providers DNS Server IP?
Is this view correct or should all router users always enter 192.168.0.1 as primary DNS server?
Assume I enter another external DNS server (like OpenDNS or GoogleDNS) in the Win 7 LAN settings.
When is this second DNS server called? Only then when the first shows no response (=in case of failure)?
Or are DNS requests always broadcasted to both defined DNS servers and Win 7 waits for the faster response of them?
That would produce overhead traffic.
Peter
In the past I have always setup the router IP 192.168.0.1 as DNS server in the Win 7 LAN settings dialog.
Does that make sense?
Because the router hardware itself does not contain a DNS server (or at least with some very poor caching) he has most of the time forward all DNS request from e.g. my notebook to the outside broadband providers DNS server.
So why not entering directly the broadband providers DNS Server IP?
Is this view correct or should all router users always enter 192.168.0.1 as primary DNS server?
Assume I enter another external DNS server (like OpenDNS or GoogleDNS) in the Win 7 LAN settings.
When is this second DNS server called? Only then when the first shows no response (=in case of failure)?
Or are DNS requests always broadcasted to both defined DNS servers and Win 7 waits for the faster response of them?
That would produce overhead traffic.
Peter