<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Jeremy&#039;s Weblog &#187; dns</title>
	<atom:link href="http://blog.jolexa.net/tag/dns/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jolexa.net</link>
	<description>Random thoughts and rants...mostly Linux</description>
	<lastBuildDate>Fri, 03 Feb 2012 16:49:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Gentoo: Easy way to ditch your ISP nameserver</title>
		<link>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/</link>
		<comments>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 16:32:39 +0000</pubDate>
		<dc:creator>Jeremy Olexa</dc:creator>
				<category><![CDATA[gentoo]]></category>
		<category><![CDATA[dns]]></category>
		<category><![CDATA[linode]]></category>

		<guid isPermaLink="false">http://blog.jolexa.net/?p=619</guid>
		<description><![CDATA[My linode is now my personal DNS resolver. I have officially ditched the ISP nameservers from this point forward now that I found unbound. Unbound is a lightweight, recursive resolver that is perfect for your LAN, co-located host, or even a single host. For your single host, emerge unbound, start the service, add 127.0.0.1 to [...]]]></description>
			<content:encoded><![CDATA[<p>My <a href="http://blog.jolexa.net/tag/linode/">linode</a> is now my <em>personal</em> DNS resolver. I have officially ditched the ISP nameservers from this point forward now that I found <a href="http://unbound.net/">unbound</a>. Unbound is a lightweight, recursive resolver that is perfect for your LAN, co-located host, or even a single host.</p>
<p>For your single host, <code>emerge unbound</code>, start the service, add 127.0.0.1 to the first nameserver in <code>/etc/resolv.conf</code>. Unbound is setup (by default) to accept connections from localhost and refuse anything else. <strong>If</strong> you are using dhcp at home (likely) then also <code>emerge openresolv</code> and uncomment <code>name_servers=127.0.0.1</code> in <code>/etc/resolvconf.conf</code>, openresolv then &#8220;intercepts&#8221; dhcpcd when it tries to write to <code>/etc/resolv.conf</code> and adds 127.0.0.1 as your first nameserver <img src='http://blog.jolexa.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  For your LAN, just configure your router to look to the host that you setup unbound on, with additional configuration.</p>
<p>Finally, you can also have unbound run on your co-located host. Just edit <code>/etc/unbound/unbound.conf</code> to a) listen on an outside interface and b) allow your other host to query it. This will be left as an exercise for the reader, it is easy to figure out.</p>
<p>Lastly, a shout-out to Linux Gazette for an excellent write-up on <a href="http://linuxgazette.net/170/googledns.html">GoogleDNS</a> (and why you should use something like unbound) and <a href="http://linuxgazette.net/170/lan.html">DNS/LAN metaphors</a>. Suggested reading if you feel out of your league with DNS internals, like me. <img src='http://blog.jolexa.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>A quote from the above linked article: <strong>&#8220;<em>Why outsource to anyone, when you can do a better job locally, at basically no cost in effort?</em>&#8220;</strong> and really, that is the truth. Have fun.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jolexa.net/2010/01/12/gentoo-easy-way-to-ditch-your-isp-nameserver/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>

