Difference between revisions of "Talk:Dnsmasq"

From ArchWiki
Jump to: navigation, search
(Created page with '== Testing without "http://" == In the test section it is recommended that the reader tries dig http://archlinux.org | grep "Query time" However, on both my systems running dnsm…')
 
(Dnsmasq and Pidgin/Gtalk: new section)
(11 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Testing without "http://" ==
+
== need information for fixed IPs ==
In the test section it is recommended that the reader tries
+
when this is set in rc.conf I think that require :
  dig http://archlinux.org | grep "Query time"
+
  { echo "nameserver 127.0.0.1"; grep -v "^#" /etc/resolv.conf | head -2; } > /tmp/resolv.conf
However, on both my systems running dnsmasq-2.50, querying anything prefixed with a "http://" causes dnsmasq to automatically forward the query and not to cache the reply:
+
then backup /etc/resolv.conf and last :
  % dig "http://archlinux.org" | grep "Query time"; !#
+
  mv /tmp/resolv.conf /etc/resolv.conf
;; Query time: 493 msec
+
--[[User:Sputnick|Sputnick]] 17:59, 1 August 2011 (EDT)
;; Query time: 485 msec
+
: 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)
The daemon logs
+
 
dnsmasq: forwarded query to 208.67.220.220
+
== Force DNS cache persistence? ==
dnsmasq: forwarded query to 208.67.220.220
+
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)
This might lead the reader to think dnsmasq is not working, when it actually works fine with:
+
 
% dig "archlinux.org" | grep "Query time"; !#
+
== Dnsmasq and Pidgin/Gtalk ==
;; Query time: 508 msec
+
 
;; Query time: 0 msec
+
Using dnsmasq for dns caching seems to break gtalk on pidgin. Editing /etc/dhcpcd.conf and adding
The daemon logs
+
option 'domainneed' '1' solves the issue on my machine.
dnsmasq: query[A] archlinux.org from 127.0.0.1
+
 
dnsmasq: forwarded archlinux.org to 208.67.222.222
+
if others verify the issue and fix, maybe consider for addition to the wiki?
dnsmasq: forwarded archlinux.org to 208.67.220.220
+
 
dnsmasq: reply archlinux.org is 66.211.214.131
+
[[User:LiamMcCalloway|LiamMcCalloway]] ([[User talk:LiamMcCalloway|talk]]) 01:10, 11 June 2013 (UTC) Liam
dnsmasq: query[A] archlinux.org from 127.0.0.1
+
dnsmasq: cached archlinux.org is 66.211.214.131
+
So, I'm removing the "http://" prefix. -- [[User:Tresende|Tresende]] 11:39, 12 November 2009 (EST)
+

Revision as of 01:10, 11 June 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)

Dnsmasq and Pidgin/Gtalk

Using dnsmasq for dns caching seems to break gtalk on pidgin. Editing /etc/dhcpcd.conf and adding option 'domainneed' '1' solves the issue on my machine.

if others verify the issue and fix, maybe consider for addition to the wiki?

LiamMcCalloway (talk) 01:10, 11 June 2013 (UTC) Liam