TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Improving your resolv.conf file

33 pointsby datumsabout 15 years ago

7 comments

viraptorabout 15 years ago
There's no "why". There's no justification for the word "improving" either. No interesting content really.<p>Even the man page is better: <a href="http://linux.die.net/man/5/resolv.conf" rel="nofollow">http://linux.die.net/man/5/resolv.conf</a><p>"Optimised" resolv.conf has one line - 127.0.0.1 and the host runs a local cache (dnsmasq / bind / djbdns / ...)
评论 #1311291 未加载
skorguabout 15 years ago
&#62; nameserver 4.4.4.4<p>Please don't do this unless you're a GTE/Verizon customer. Use your ISP's or run a resolver yourself.
评论 #1312211 未加载
评论 #1311414 未加载
mhansenabout 15 years ago
Try out namebench. It hunts down the fastest DNS servers available for your computer to use. namebench runs a fair and thorough benchmark using your web browser history, tcpdump output, or standardized datasets in order to provide an individualized recommendation.<p><a href="http://code.google.com/p/namebench/" rel="nofollow">http://code.google.com/p/namebench/</a>
egonzalezabout 15 years ago
@viraptor thanks for the feedback. Excluding the "why" was a huge oversight. As far as running a local resolver, it depends on how you architect your infrastructure. Having a single line with 127.0.0.1 introduces a single point of failure. While that might be acceptable for demo/prototyping applications, I think for production deployments you'd want to avoid that. Also running a local resolver adds another service you'll need to monitor and keep up to date.<p>Note: This recommendation is for server setups, where dns latency can easily add ms to processing time. With workstations we can tolerate some latency and should probably benchmark your ISPs resolvers.
qbiabout 15 years ago
I wrote an additional entry on how to find to optimal nameserver: <a href="http://www.kubieziel.de/blog/archives/1343-Improving-your-resolv.conf-file-part-2.html" rel="nofollow">http://www.kubieziel.de/blog/archives/1343-Improving-your-re...</a>
sandGorgonabout 15 years ago
hmmm.. what distro is this ?<p>Because AFAIK, ubuntu distros (and maybe redhat/fedora even) suffer from multisecond delays due to ipv6 lookups - <a href="https://bugs.launchpad.net/ubuntu/lucid/+source/eglibc/+bug/417757" rel="nofollow">https://bugs.launchpad.net/ubuntu/lucid/+source/eglibc/+bug/...</a><p>I thought this article had some solution to that (other than disabling ipv6, right now) - but dont think so
knownabout 15 years ago
<a href="http://www.dnsserverlist.org/indexbeta.php?oby=Q_RTT" rel="nofollow">http://www.dnsserverlist.org/indexbeta.php?oby=Q_RTT</a>