[Bug 998712] Re: dnsmasq integration into name resolution broken
** Changed in: dnsmasq (Ubuntu) Status: Invalid = Incomplete -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
On the affected system when it is manifesting the problem you reported (can't resolve names), is named running locally? (In your original submission you said that bind was running.) What role does this named play in your network? How is it configured? What happens if you stop this named? And then restart network-manager? All these questions pertain, obviously, to the hypothesis that local named may be interfering with local dnsmasq. -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
Thomas, there is no local named on any notebook here. dnsmasq does not interfere with named on any of my machines. It should actually not even be possible. As far as I am concerned, the bind() request should return false and give an EADDRINUSE if the socket was already bound by something. Unless dnsmasq uses a different technique to attach itself to port 53. -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
The hypothesis was that named started before dnsmasq, preventing dnsmasq from binding port 53 on 127.0.0.1. But the hypothesis is false, since you are not running named after all. Returning to your dig output, it can be summarized as follows. dig s4 - FAILURE dig @10.1.0.4 s4 - FAILURE dig @10.1.0.4 s4.rsb.intern - SUCCESS (Wolf did something here) dig s4 - FAILURE ping s4 - SUCCESS Notice that domain name completion failed even when the external server was specified. As Simon wrote in #4, domain name completion happens in the resolver library. So there seems to be something wrong with the resolver library: it doesn't complete domain names with the domain search suffixes when dnsmasq is in use. Am I right? Does dig @127.0.0.1 s4.rsb.intern work on the affected system running NM-controlled dnsmasq? ** Summary changed: - dnsmasq integration into name resolution broken + domain name completion broken when dnsmasq is used -- 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: domain name completion broken when dnsmasq is used 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
In fact my point of view is that I have submitted all information I could provide in reasonable time. Give me a bunch of experiments I have to carry out, I'll spend an afternoon to help resolve the issue From my point of view, I have given you more than enough input to localise the issue (see other bugs as well). Feel free to drop. The issue is still here. -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
Please understand that I don't have the time OK, marking this as invalid. ** Changed in: dnsmasq (Ubuntu) Status: Incomplete = Invalid -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
I'd just like to note here before leaving this issue that the submitter originally said that he was running bind. If bind was set up to listen on 127.0.0.1#53 but was not correctly set up to provide name service then I imagine that this could have interfered with the NM-controlled dnsmasq. Exploring this possibility would have required cooperation by the submitter, but, unfortunately, the submitter is no longer willing to cooperate because he lacks time and has found a workaround that he is satisfied with. -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
Wolf: You list problems with dnsmasq. In this report (#998712) let's continue to discuss the name resolution failure that you originally reported. One of the other problems you listed is being discussed in #1003842. For the remaining problems you listed, please submit your information to bug reports (possibly newly opened by you) focusing on those problems. Let's talk about the situation where name resolution fails on your system. When you have the following... /etc/resolv.conf: nameserver 127.0.0.1 search rsb.intern rsb.at /var/run/nm-dns-dnsmasq.conf server=192.168.0.1 ... what is the output of ps -elf|grep dnsmasq? -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
My /var/run/nm-dns-dnsmasq.conf contained server=10.1.0.4 server=10.1.0.254 server=195.202.128.3 wolf@mbp:~$ ps -elf | grep dnsmasq 4 S nobody 25661 25624 0 80 0 - 7579 poll_s 15:20 ?00:00:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.0.1 --conf-file=/var/run/nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec 0 S wolf 25774 25489 0 80 0 - 2720 pipe_w 15:21 pts/100:00:00 grep --color=auto dnsmasq wolf@mbp:~$ Thomas, please understand that I don't have the time to reiterate on situations that I have solved by reverting back to the original state. I gave you enough hints to solve the issue. You can set up a situation like mine in a bunch of virtual machines and simulate the effects. I have a solution by disabling dnsmasq in network manager. You might as well close this incident. But this will not fix the bug. -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
Wolf: Please post the FULL contents of your /etc/resolv.conf file as it is when the reported problem occurs. -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
Wolf: In #3 you post some output but I don't know how to interpret it. You start with a ping s4 which yields unknown host. You end with ping s4 which successfully pings. What happened in the meantime to change the results? Did you edit something? -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
The /etc/resolv.conf held just a reference to 127.0.0.1 # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search rsb.intern rsb.at I copied a working version over it: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.1.0.4 nameserver 10.1.0.254 nameserver 195.202.128.3 search rsb.intern rsb.at That way, name resolution worked immediately. This brings back the old and stable name resolution. As far as I can observe this, no side effects as you discussed in #1003842 So far I have disabled dnsmasq in /etc/NetworkManager/NetworkManager.conf Currently my view is that dnsmasq has some serious issues: - name resolution in mixed DNS setups - handling of refreshes of network manager (happens periodically with calls to resolvconf, aperiodically when new SSIDs emerge, network media changes or the machine is put into sleep mode) - VPN management (which requires several different domains to be intersected) - caching of resolved names - handling of /etc/hosts Hope this helps. -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
** Changed in: dnsmasq (Ubuntu) Status: New = Incomplete -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
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
Re: [Bug 998712] Re: dnsmasq integration into name resolution broken
On 17/05/12 10:19, Wolf Rogner wrote: 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:~$ The difference between the working and non-working examples is that the non-working ones are looking up s4. and the working ones are looking up s4.rsb.intern. getting from ssh s4 to a DNS lookup of the A record s4.rsb.intern, is the responsibilty of the C library resolver, which is configured by /etc/resolv.conf. There are a few parameters in there that can affect things, look for domain, search and options ndots. Are there differences in these parameters between the working and non-working states? Simon. -- 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
[Bug 998712] Re: dnsmasq integration into name resolution broken
-- 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
