I recreated the situation by restarting the network manager. resolv.conf contains link to 127.0.0.1 /run/nm-dns-dnsmasq.conf contained my name server already.
However, even dig does not resolv correctly. Here are the results (my network is 10.x.x.x actually) wolf@mbp:~$ ping s4 ping: unknown host s4 wolf@mbp:~$ dig s4 ; <<>> DiG 9.8.1-P1 <<>> s4 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27930 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;s4. IN A ;; Query time: 3 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Thu May 17 11:07:39 2012 ;; MSG SIZE rcvd: 20 wolf@mbp:~$ dig @10.1.0.4 s4 ; <<>> DiG 9.8.1-P1 <<>> @10.1.0.4 s4 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34081 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;s4. IN A ;; AUTHORITY SECTION: . 10800 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2012051700 1800 900 604800 86400 ;; Query time: 21 msec ;; SERVER: 10.1.0.4#53(10.1.0.4) ;; WHEN: Thu May 17 11:07:50 2012 ;; MSG SIZE rcvd: 95 wolf@mbp:~$ dig @10.1.0.4 s4.rsb.intern ; <<>> DiG 9.8.1-P1 <<>> @10.1.0.4 s4.rsb.intern ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35717 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;s4.rsb.intern. IN A ;; ANSWER SECTION: s4.rsb.intern. 34000 IN A 10.1.0.4 ;; AUTHORITY SECTION: rsb.intern. 34000 IN NS s4.rsb.intern. ;; Query time: 3 msec ;; SERVER: 10.1.0.4#53(10.1.0.4) ;; WHEN: Thu May 17 11:08:03 2012 ;; MSG SIZE rcvd: 61 wolf@mbp:~$ less /run/nm-dns-dnsmasq.conf wolf@mbp:~$ dig s4 ; <<>> DiG 9.8.1-P1 <<>> s4 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18553 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;s4. IN A ;; AUTHORITY SECTION: . 10725 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2012051700 1800 900 604800 86400 ;; Query time: 14 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Thu May 17 11:09:05 2012 ;; MSG SIZE rcvd: 95 wolf@mbp:~$ ping s4 PING s4.rsb.intern (10.1.0.4) 56(84) bytes of data. ^X^C64 bytes from 10.1.0.4: icmp_req=1 ttl=64 time=0.792 ms --- s4.rsb.intern ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.792/0.792/0.792/0.000 ms wolf@mbp:~$ I have not quite figured out what exactly happens. It takes about 1 to 30 minutes to resolve the issue. On some machines it never settles itself. Certainly, if I manually adjust /etc/resolv.conf everthing works fine immediately (name resolution, access to services). If I keep the files the way they are, it is pure coincidence whether dns works (I had the chance to use a wired LAN recently and it seems to be the same issue there). My guess would be that network manager and dns-mask do not work together in all cases (in fact, they do cooperate only in just one case, after a reboot). As I never reboot machines (if I don't have to), I put machines to sleep, connect, disconnect, I practically never run into the optimal situation. Hope this helps. Wolf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
