Comment 0 for bug 998712

dnsmasq does not resolve DNS names correcty.

Applications like Thunderbird or tools like ssh rely on working name resolution. However, if there never was a working name resolution, dnsmasq never gets to know about the DNS names.

Setup:

private network: 192.168.0.x/24
domain mydomain.intern
server: 192.168.0.1 hostname s1
dhcp (.100 - .200) and bind running, postfix and dovecot running
client: 192.168.0.100 (dhclient)

/etc/resolv.conf
...
nameserver 127.0.0.1
search mydomain.intern

/var/run/nm-dns-dnsmasq.conf
server=192.168.0.1

Open Thunderbird -> Thunderbird fails to open s1
ssh admin@s1 -> ssh: Could not resolve hostname s1: Name or service not known

Adding
nameserver 192.168.0.1
to /etc/resolv.conf

resolves the issue immediately

calling sudo resolvconf -u

creates the lookup problem immediately again

This is a critical error

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: dnsmasq-base 2.59-4
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sun May 13 11:43:02 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to precise on 2012-04-29 (13 days ago)