<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Gentoo: Easy way to ditch your ISP nameserver</title>
	<atom:link href="http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/</link>
	<description>Random thoughts and rants...mostly Linux</description>
	<lastBuildDate>Mon, 06 Sep 2010 12:28:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Paul</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1868</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 28 Jan 2010 21:20:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1868</guid>
		<description>Thanks for the article, it&#039;s exactly what I needed. I had something set up like this previously with djbdns but got lost in a system upgrade and never found the time to do it again. These instructions were nice and easy.

To the people who say to use the ISP nameserver: my ISP nameservers are horribly slow and often timeout, they resolve invalid hostames (to point to their ad-infested error page), sometimes resolve valid hostnames as their ad-page as well, and they sell customer&#039;s DNS lookup history to companies for targeted advertising. No thanks!</description>
		<content:encoded><![CDATA[<p>Thanks for the article, it&#8217;s exactly what I needed. I had something set up like this previously with djbdns but got lost in a system upgrade and never found the time to do it again. These instructions were nice and easy.</p>
<p>To the people who say to use the ISP nameserver: my ISP nameservers are horribly slow and often timeout, they resolve invalid hostames (to point to their ad-infested error page), sometimes resolve valid hostnames as their ad-page as well, and they sell customer&#8217;s DNS lookup history to companies for targeted advertising. No thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1862</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 25 Jan 2010 01:43:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1862</guid>
		<description>dnsmasq is not just a forwarder; it caches as many external lookups as you configure it to, and it maintains local records (e.g., for local use behind NAT).  So it does do its own lookups, both from cache and from local records; if forwards requests for whatever it doesn&#039;t have a record of.

Also, you do some benchmarking, you&#039;ll find that using GoogleDNS is almost never the fastest option, and that using local ISP nameservers is almost always the fastest option.  Google&#039;s benchmarking app only pays attention to the actual transaction time (the lookup time), and while their centralized servers (and the centralized servers of similar providers, such as opendns) do perform faster lookups, this time reduction is more than offset by the increase in the time it takes for packets to get back and forth between you and their servers.  Try is by comparing a few &#039;time nslookup xxx.xxx.xxx.xxx&#039; operations (being sure to avoid caching artificialities).</description>
		<content:encoded><![CDATA[<p>dnsmasq is not just a forwarder; it caches as many external lookups as you configure it to, and it maintains local records (e.g., for local use behind NAT).  So it does do its own lookups, both from cache and from local records; if forwards requests for whatever it doesn&#8217;t have a record of.</p>
<p>Also, you do some benchmarking, you&#8217;ll find that using GoogleDNS is almost never the fastest option, and that using local ISP nameservers is almost always the fastest option.  Google&#8217;s benchmarking app only pays attention to the actual transaction time (the lookup time), and while their centralized servers (and the centralized servers of similar providers, such as opendns) do perform faster lookups, this time reduction is more than offset by the increase in the time it takes for packets to get back and forth between you and their servers.  Try is by comparing a few &#8216;time nslookup xxx.xxx.xxx.xxx&#8217; operations (being sure to avoid caching artificialities).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Olexa</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1854</link>
		<dc:creator>Jeremy Olexa</dc:creator>
		<pubDate>Wed, 20 Jan 2010 18:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1854</guid>
		<description>Convince ISPs to get their act together then. Until that happens, I&#039;m going to use something that works...</description>
		<content:encoded><![CDATA[<p>Convince ISPs to get their act together then. Until that happens, I&#8217;m going to use something that works&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1853</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 20 Jan 2010 18:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1853</guid>
		<description>All well and good, but remember that caching DNS server&#039;s are there in your ISP&#039;s network for a good reason. If everyone started doing this the extra load on the root servers (See http://www.root-servers.org/) would go up and could adversely impact the service they provide. Granted it would take a fair few networks to do it but the root servers really shouldn&#039;t be requested against directly unless need demands it (or you are, for an example, a major ISP).

It&#039;s all about spreading the load properly around the networks.

Note also, that while lookup&#039;s after the first request will be quicker (that&#039;s a given, it&#039;s cached and on your network sub 1ms from your machine in most cases) the first request can, and does at times, take a long time compared to hitting the ISP DNS Cache. Something that isn&#039;t mentioned above.

Don&#039;t forget that many ISP&#039;s will also not provide support if you have &quot;non-standard&quot; network setups so you may want to note the old settings for testing if something goes wrong...</description>
		<content:encoded><![CDATA[<p>All well and good, but remember that caching DNS server&#8217;s are there in your ISP&#8217;s network for a good reason. If everyone started doing this the extra load on the root servers (See <a href="http://www.root-servers.org/)" rel="nofollow">http://www.root-servers.org/)</a> would go up and could adversely impact the service they provide. Granted it would take a fair few networks to do it but the root servers really shouldn&#8217;t be requested against directly unless need demands it (or you are, for an example, a major ISP).</p>
<p>It&#8217;s all about spreading the load properly around the networks.</p>
<p>Note also, that while lookup&#8217;s after the first request will be quicker (that&#8217;s a given, it&#8217;s cached and on your network sub 1ms from your machine in most cases) the first request can, and does at times, take a long time compared to hitting the ISP DNS Cache. Something that isn&#8217;t mentioned above.</p>
<p>Don&#8217;t forget that many ISP&#8217;s will also not provide support if you have &#8220;non-standard&#8221; network setups so you may want to note the old settings for testing if something goes wrong&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Nelson</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1839</link>
		<dc:creator>Mike Nelson</dc:creator>
		<pubDate>Mon, 18 Jan 2010 15:59:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1839</guid>
		<description>Thanks for this, Jeremy. I&#039;m now using unbound locally as well. Those linked articles went a long way in helping me understand DNS better. There has always been a bit of a mystery there for me.</description>
		<content:encoded><![CDATA[<p>Thanks for this, Jeremy. I&#8217;m now using unbound locally as well. Those linked articles went a long way in helping me understand DNS better. There has always been a bit of a mystery there for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Olexa</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1835</link>
		<dc:creator>Jeremy Olexa</dc:creator>
		<pubDate>Fri, 15 Jan 2010 23:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1835</guid>
		<description>Well, dnsmasq is just a forwarder. So, it is not the one that is doing any lookups. dnsmasq is running on my router as well, it gets it data from a resolver (unbound in my case).</description>
		<content:encoded><![CDATA[<p>Well, dnsmasq is just a forwarder. So, it is not the one that is doing any lookups. dnsmasq is running on my router as well, it gets it data from a resolver (unbound in my case).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yogesh Sharma</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1834</link>
		<dc:creator>Yogesh Sharma</dc:creator>
		<pubDate>Fri, 15 Jan 2010 23:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1834</guid>
		<description>I have been using dnsmasq which also provides DHCP to LAN clients along with DNS</description>
		<content:encoded><![CDATA[<p>I have been using dnsmasq which also provides DHCP to LAN clients along with DNS</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Yarych</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1833</link>
		<dc:creator>Ivan Yarych</dc:creator>
		<pubDate>Thu, 14 Jan 2010 14:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1833</guid>
		<description>Personally I use tinydns&#039; dnscache - works very fast! very reliable! installed in minutes as well.
I don&#039;t get why use Google&#039;s DNS on different continent when you can use your own one near you? :)</description>
		<content:encoded><![CDATA[<p>Personally I use tinydns&#8217; dnscache &#8211; works very fast! very reliable! installed in minutes as well.<br />
I don&#8217;t get why use Google&#8217;s DNS on different continent when you can use your own one near you? <img src='http://blog.jolexa.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1828</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 14 Jan 2010 00:07:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1828</guid>
		<description>Thank you, very enlightening content and links.

I&#039;d be interested to learn if you have noticed a performance increase (either with your own eyes or with a tool to measure network/DNS performance).</description>
		<content:encoded><![CDATA[<p>Thank you, very enlightening content and links.</p>
<p>I&#8217;d be interested to learn if you have noticed a performance increase (either with your own eyes or with a tool to measure network/DNS performance).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stjujsckij Nickolaj</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/comment-page-1/#comment-1823</link>
		<dc:creator>Stjujsckij Nickolaj</dc:creator>
		<pubDate>Wed, 13 Jan 2010 11:37:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=619#comment-1823</guid>
		<description>Another way is to use net-misc/dhcpcd and customize /etc/resolv.conf.{head,tail} files.</description>
		<content:encoded><![CDATA[<p>Another way is to use net-misc/dhcpcd and customize /etc/resolv.conf.{head,tail} files.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
