From ArchWiki
Revision as of 03:35, 30 August 2012 by Mrpsbrk (talk | contribs) (Easier way to work with NetworkManager: new section)
Jump to: navigation, search



Testing without "http://"

In the test section it is recommended that the reader tries

dig | grep "Query time"

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:

% dig "" | grep "Query time"; !#
;; Query time: 493 msec
;; Query time: 485 msec

The daemon logs

dnsmasq: forwarded query to
dnsmasq: forwarded query to

This might lead the reader to think dnsmasq is not working, when it actually works fine with:

% dig "" | grep "Query time"; !#
;; Query time: 508 msec
;; Query time: 0 msec

The daemon logs

dnsmasq: query[A] from
dnsmasq: forwarded to
dnsmasq: forwarded to
dnsmasq: reply is
dnsmasq: query[A] from
dnsmasq: cached is

So, I'm removing the "http://" prefix. -- Tresende 11:39, 12 November 2009 (EST)

need information for fixed IPs

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

{ echo "nameserver"; 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)

Easier way to work with NetworkManager

Supposedly, if you add a line like


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 will test this and report back whether it works...

Mrpsbrk (talk) 03:35, 30 August 2012 (UTC)