Reuben Thomas wrote:
Package: dnsmasq
Version: 2.35-1
Severity: normal
I had dnsmasq installed, but not resolvconf. When I started up
dnsmasq, it said it was reading entries from /etc/hosts (or
equivalently, /etc/banner_add_hosts, which I also tried with the same
contents). Other machines on the local net had the server's address as
their DNS server, but when asking for addresses for names in its
/etc/hosts, they were not found.
The hosts's own DNS servers were set to upstream DNS servers.
On installing resolvconf, everything straightened out. Of course, now
the hosts's own DNS server was set to 127.0.0.1, i.e. using dnsmasq,
but I'm unclear as to why this should make a difference to DNS
requests from its clients, which were still talking to dnsmasq as
before.
It's not clear exactly what's happening here, or if there's even a
problem. One explanation might be that the server running dnsmasq was
also running a Web proxy, and the DNS activity was generated by HTTP
traffic. In that case the DNS lookups are done by the proxy, so they
would fail before /etc/resolv.conf on server was updated.
Cheers,
Simon.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]