[Dnsmasq-discuss] Mysterious dnsmasq 2.38 'hangs'
bod at bod.org
Fri Feb 16 22:11:54 GMT 2007
/etc/nsswitch.conf is untouched, so it does indeed have:
hosts: files dns
All the aliases for that machine are indeed in /etc/hosts.
With regards to your earlier question: It's not _sending_ logging info
to a remote server, but it is _receiving_ remote logging packets from my
colocation server. Incoming remote logging traffic is pretty low,
though. But come to think of it, the colocation server's name isn't in
the hosts file, so when syslog looks that up, it may cause dnsmasq to
send a request upstream.
Anyhow, I've finished converting all the 'syslog(LOG_<SOMETHING>, ...)'
into 'log_<something>(...)' calls, and added log_debug(), log_info(),
log_warning(), and log_error() functions into utils.c that just use
vfprintf to stderr (i.e. no syslog() calls). The hacked version is
running now, with the -d option. But it'll take a few hours before I'll
know if it made any difference.
BTW, I'm using two openDNS nameservers upstream, along with the two my
ISP provides. The openDNS servers are great, very responsive and
reliable, but they do return a bogus nxdomain for lookup failures,
though they're actually using it for good reason - if a web browser then
connects to the wildcard domain they returned, it serves a web page with
a google search for the words in the domain name you (mis)typed. As an
aside, I'd find it useful to be able to restrict the effect of
'bogus-nxdomain' to lookups in a given domain, as the openDNS behavior
is actually useful - I just don't want it for lookups within my local
> -----Original Message-----
> From: Simon Kelley [mailto:simon at thekelleys.org.uk]
> Sent: Friday, February 16, 2007 1:24 PM
> To: Paul Chambers
> Cc: dnsmasq-discuss at lists.thekelleys.org.uk
> Subject: Re: [Dnsmasq-discuss] Mysterious dnsmasq 2.38 'hangs'
> Further to my syslog-deadlock theory, Google came up with
> this, which is old, but looks plausible.
> What do you have in /etc/nsswitch.conf on the machine running
> given that syslog has to lookup it's own address using
> gethostbyaddr(), and that all the aliases should be in
> /etc/hosts, then one could imagine that having
> hosts: files dns
> would be good, but having
> hosts: dns files
> would be bad.
More information about the Dnsmasq-discuss