<?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: Fixing NetworkManager DNS issue in Ubuntu (Hardy Heron/Gutsy)</title>
	<atom:link href="http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/</link>
	<description>01100010 01101100 01100101 01101000</description>
	<lastBuildDate>Sun, 29 Aug 2010 12:18:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: arky</title>
		<link>http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/comment-page-1/#comment-227901</link>
		<dc:creator>arky</dc:creator>
		<pubDate>Sun, 22 Aug 2010 03:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/#comment-227901</guid>
		<description>Tried this on Ubuntu 10.04, it works well! Thank you</description>
		<content:encoded><![CDATA[<p>Tried this on Ubuntu 10.04, it works well! Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ezekiel</title>
		<link>http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/comment-page-1/#comment-217691</link>
		<dc:creator>Ezekiel</dc:creator>
		<pubDate>Wed, 14 Oct 2009 09:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/#comment-217691</guid>
		<description>Overiding /etc/resolver.conf  access rights really did it for me. 

chmod -w /etc/resolver.conf</description>
		<content:encoded><![CDATA[<p>Overiding /etc/resolver.conf  access rights really did it for me. </p>
<p>chmod -w /etc/resolver.conf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl</title>
		<link>http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/comment-page-1/#comment-184010</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Tue, 09 Dec 2008 20:12:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/#comment-184010</guid>
		<description>I tried both of these.  Neither worked.  I have used dhclient.conf to maintain my caching nameserver as the first entry in my resolv.conf file for years.  Now, it really seems that NetworkManager has taken over stewardship of this file and does not provide a mechanism that replaces the old dhclient.conf prepend directive.  This is a shame.  They&#039;ve missed the mark.  Instead of making networking painless for me they&#039;ve made it more painful.

Anyway, I decided that the easiest way out of this situation for me was to write this script which inserts localhost as the first name server regardless of who wants to own /etc/resolv.conf.  (BTW, I used dnsmasq for DNS caching on my laptop)

% cat /etc/resolv.conf.fix
if [ ! -t 0 ]; then
    exec &gt; /dev/null 2&gt;&amp;1
fi

if ! grep -q 0.0.0.0 /etc/resolv.conf; then
    ed /etc/resolv.conf &lt;&lt; EOF
/^nameserver
i
nameserver 0.0.0.0
.
w
q
EOF
fi

Then, I added a cron entry in to root&#039;s cron table to run this every minute.

I really didn&#039;t like this solution but it was quick and dirty.  It is not a good long-term solution.  The best solution will be to fix NetworkManager to leave it alone or to allow prepending of nameservers into this file.</description>
		<content:encoded><![CDATA[<p>I tried both of these.  Neither worked.  I have used dhclient.conf to maintain my caching nameserver as the first entry in my resolv.conf file for years.  Now, it really seems that NetworkManager has taken over stewardship of this file and does not provide a mechanism that replaces the old dhclient.conf prepend directive.  This is a shame.  They&#8217;ve missed the mark.  Instead of making networking painless for me they&#8217;ve made it more painful.</p>
<p>Anyway, I decided that the easiest way out of this situation for me was to write this script which inserts localhost as the first name server regardless of who wants to own /etc/resolv.conf.  (<span class="caps">BTW</span>, I used dnsmasq for <span class="caps">DNS</span> caching on my laptop)</p>
<p>% cat /etc/resolv.conf.fix<br />
if [ ! -t 0 ]; then<br />
    exec &gt; /dev/null 2&gt;&amp;1<br />
fi</p>
<p>if ! grep -q 0.0.0.0 /etc/resolv.conf; then<br />
    ed /etc/resolv.conf &lt;&lt; <span class="caps">EOF</span><br />
/^nameserver<br />
i<br />
nameserver 0.0.0.0<br />
.<br />
w<br />
q<br />
<span class="caps">EOF</span><br />
fi</p>
<p>Then, I added a cron entry in to root&#8217;s cron table to run this every minute.</p>
<p>I really didn&#8217;t like this solution but it was quick and dirty.  It is not a good long-term solution.  The best solution will be to fix NetworkManager to leave it alone or to allow prepending of nameservers into this file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shinzies</title>
		<link>http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/comment-page-1/#comment-182766</link>
		<dc:creator>shinzies</dc:creator>
		<pubDate>Mon, 01 Dec 2008 21:20:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/#comment-182766</guid>
		<description>Thanks Mikhail
Your solution seems to be working fine for me as well.
Very Good Tip!!!</description>
		<content:encoded><![CDATA[<p>Thanks Mikhail<br />
Your solution seems to be working fine for me as well.<br />
Very Good Tip!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lennart</title>
		<link>http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/comment-page-1/#comment-163864</link>
		<dc:creator>lennart</dc:creator>
		<pubDate>Sat, 20 Sep 2008 10:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/#comment-163864</guid>
		<description>First solution did work for me. Tnx!</description>
		<content:encoded><![CDATA[<p>First solution did work for me. Tnx!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gasull</title>
		<link>http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/comment-page-1/#comment-127882</link>
		<dc:creator>gasull</dc:creator>
		<pubDate>Fri, 23 May 2008 15:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejackol.com/2008/05/20/fixing-networkmanager-dns-issue-in-ubuntu-hardy-herongutsy/#comment-127882</guid>
		<description>That didn&#039;t work for me, because then the nm-applet takes forever trying to modify /etc/resolv.conf, and I never get a working Internet connection.

The solution is to edit /etc/dhcp3/dhclient.conf with the following line:

prepend domain-name-servers 208.67.222.222,208.67.220.220;

With the IP&#039;s above you will be using the OpenDNS servers.

http://ubuntu.wordpress.com/2006/08/02/local-dns-cache-for-faster-browsing/</description>
		<content:encoded><![CDATA[<p>That didn&#8217;t work for me, because then the nm-applet takes forever trying to modify /etc/resolv.conf, and I never get a working Internet connection.</p>
<p>The solution is to edit /etc/dhcp3/dhclient.conf with the following line:</p>
<p>prepend domain-name-servers 208.67.222.222,208.67.220.220;</p>
<p>With the IP&#8217;s above you will be using the OpenDNS servers.</p>
<p><a href="http://ubuntu.wordpress.com/2006/08/02/local-dns-cache-for-faster-browsing/" rel="nofollow">http://ubuntu.wordpress.com/2006/08/02/local-dns-cache-for-faster-browsing/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
