On 13/05/12 11:00, Wolf Rogner wrote: > Public bug reported: > > 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
Please could you add the output from dig s1 run when DNS is broken to this bug report, also dig @192.168.0.1 s1 Cheers, Simon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998712 Title: dnsmasq integration into name resolution broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/998712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
