Activity log for bug #998712

Date Who What changed Old value New value Message
2012-05-13 10:00:31 Wolf Rogner bug added bug
2012-05-14 12:10:44 Chuck Bearden bug added subscriber Chuck Bearden
2012-05-17 08:39:39 James Page dnsmasq (Ubuntu): status New Incomplete
2012-06-01 07:46:55 Thomas Hood bug added subscriber Thomas Hood
2012-06-02 15:33:38 Thomas Hood dnsmasq (Ubuntu): status Incomplete Invalid
2012-06-04 06:03:47 Thomas Hood dnsmasq (Ubuntu): status Invalid Incomplete
2012-06-04 19:28:17 Thomas Hood summary dnsmasq integration into name resolution broken domain name completion broken when dnsmasq is used
2012-06-08 00:14:46 Reggie McMurtrey bug added subscriber Reggie McMurtrey
2012-08-27 04:17:55 Launchpad Janitor dnsmasq (Ubuntu): status Incomplete Expired
2012-10-30 10:05:14 Thomas Hood dnsmasq (Ubuntu): status Expired New
2012-11-04 10:26:06 Thomas Hood dnsmasq (Ubuntu): status New Incomplete
2013-02-13 04:17:40 Launchpad Janitor dnsmasq (Ubuntu): status Incomplete Expired
2013-04-09 07:50:32 Thomas Hood dnsmasq (Ubuntu): status Expired Confirmed
2013-04-09 07:51:22 Thomas Hood description 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) Dnsmasq sometimes does not resolve DNS names correcty. Sometimes it seems that 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)