[TriLUG] Revisiting local dnsmasq DNS resolution

Alan Porter porter at trilug.org
Thu Nov 1 13:32:34 EDT 2012


I'm not sure if this helps, but this is a snippet of comment that I keep 
in my /etc/dnsmasq.conf file, so I can remember the three ways I like to 
set it up.

#  (1) USE DNSMASQ FIRST, THEN TRY YOUR ISP'S DNS SERVERS
#      in this file --> comment out "resolv-file" option
#      in dhclient.conf --> prepend domain-name-servers 127.0.0.1;
#  (2) USE DNSMASQ FIRST, THEN TRY A HARD-CODED LIST OF DNS'S
#      in this file --> resolv-file=/etc/resolv.dnsmasq
#      in dhclient.conf --> prepend domain-name-servers 127.0.0.1;
#      in dhclient.dnsmasq --> search mydomain.org and nameserver list
#  (3) USE DNSMASQ ONLY, TELL DNSMASQ TO USE A HARD-CODED LIST OF DNS'S
#      in this file --> no-resolv
#      in this file --> server=208.67.222.222
#      in this file --> server=208.67.220.220
#      in this file --> bogus-nxdomain=208.69.34.132

But I don't think this is the problem.  It sounds to me like there is 
something different in the way that "host" and "dig" do their lookups 
from what all other programs do.

You don't think this is an IPv6 issue, do you?

Alan





More information about the TriLUG mailing list