On Wed, 2014-01-01 at 09:37 -0500, Greg Freemyer wrote:
Felix Miata <mrmazda@earthlink.net> wrote:
My web browsers often seem to spend a lot of time reporting "looking up host <blah>". I'd like to see less of that in 2014, and spend less time watching nothing happen in the browser's viewport.
http://www.edwin.io/optimized-resolv-conf seems to make sense, but it includes no discussion of a local nameserver, such as the one typically
enabled by default in an internet router, only using Google IPs. Anyone have anything to add or dispute what it says?
Are those using routers better off using the one it includes? Better off avoiding?
Is there any convenient way to evaluate average response times from various servers?
Are there logical reasons for avoiding Google's or other high visibility servers?
Are there reasons why the servers provided by the ISP subscribed to shouldn't be preferred?
Can anyone explain why the default timeout is 5s and not more or less? Is it a holdover from times past when the internet was less busy, and often less speedy via dialup or ISDN instead of broadband?
Felix,
I know you have numerous PCs.
Do you run your own local dns server? Since you have numerous machines you should. Set it up to forward non-cached lookups to a good dns server. No need for that good dns server to be your isp's.
Dns is a pretty lightweight service, so the recommendation even 20 years ago was to dedicate a low performance PC to dns. The reason for that is uptime for your local dns server is very important. Having a local dns server means 99% of dns lookups will be handled at local lan speeds. It also means the cache of names/ips is shared by all your machines.
Sounds like a good job for a couple of raspberry pi's (primary & secondary dns). Each of them fed from its own recharchable and PSU. hw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org