Difference between revisions of "Talk:Dnsmasq"

From ArchWiki
Jump to: navigation, search
(Testing without "http://": Remove closed discussion.)
(3 intermediate revisions by one other user not shown)
Line 5: Line 5:
 
  mv /tmp/resolv.conf /etc/resolv.conf
 
  mv /tmp/resolv.conf /etc/resolv.conf
 
--[[User:Sputnick|Sputnick]] 17:59, 1 August 2011 (EDT)
 
--[[User:Sputnick|Sputnick]] 17:59, 1 August 2011 (EDT)
 +
: Any error with direct change /etc/resolv.conf? Move around tmp is not very "Simple". -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 01:27, 20 March 2013 (UTC)
  
== Easier way to work with NetworkManager ==
+
== Force DNS cache persistence? ==
 
+
I've noticed that the DNS cache expires very quickly (less than 60 seconds) for many domains thereby defeating the purpose of caching it in the first place. Is there a way to force entries to last longer? [[User:Neounk|Neounk]] ([[User talk:Neounk|talk]]) 01:30, 31 March 2013 (UTC)
If you add a line like
+
 
+
      dns=dnsmasq
+
 
+
to /etc/NetworkManager/NetworkManager.conf then not only will NetworkManager do the right thing about resolv.conf, it will also start up dnsmasq for us, which seems way easier. I just did it in my machine and it works OK. It uses a temp conf file for dnsmasq at /var/run/nm-dns-dnsmasq.conf, and resolv.conf has only 127.0.0.1. This is not OK if dnsmasq is used for DHCP server, but is very good for caching. As it seems to me this will be the most common pattern for people using NetworkManager, i added this at the start of the NetworkManager section, instead of at the end.
+
 
+
Also, i feel that calling "DHCP config" the section about adding 127.0.0.1 to resolv.conf is very easy to confuse with configuring the DHCP functionality of dnsmasq itself. So i just changed the name to "resolv.conf".
+
 
+
[[User:Mrpsbrk|Mrpsbrk]] ([[User talk:Mrpsbrk|talk]]) 03:35, 30 August 2012 (UTC)
+
 
+
: Nice edits, Mrpsbrk.  I hadn't known about this so this is *nice*.  Cleanedup the page a bit so all is OK.  Danke --[[User:Gen2ly|Gen2ly]] ([[User talk:Gen2ly|talk]]) 23:17, 30 August 2012 (UTC)
+

Revision as of 01:30, 31 March 2013

need information for fixed IPs

when this is set in rc.conf I think that require :

{ echo "nameserver 127.0.0.1"; grep -v "^#" /etc/resolv.conf | head -2; } > /tmp/resolv.conf

then backup /etc/resolv.conf and last :

mv /tmp/resolv.conf /etc/resolv.conf

--Sputnick 17:59, 1 August 2011 (EDT)

Any error with direct change /etc/resolv.conf? Move around tmp is not very "Simple". -- Fengchao (talk) 01:27, 20 March 2013 (UTC)

Force DNS cache persistence?

I've noticed that the DNS cache expires very quickly (less than 60 seconds) for many domains thereby defeating the purpose of caching it in the first place. Is there a way to force entries to last longer? Neounk (talk) 01:30, 31 March 2013 (UTC)