[Bug 1384394] Re: /etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" command
br matching was added to interface-order in Debian release 1.77, thus in wily which has resolvconf 1.77ubuntu1. -- 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/1384394 Title: /etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1384394/+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 1536181] Re: bind9-resolvconf service doesn't work
The service is called "bind9-resolvconf" but you said you ran "sudo systemctl start bind9-resolv.conf" and "sudo systemctl stop bind9-resolv.conf". Look carefully at the spelling. ** Changed in: bind9 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1536181 Title: bind9-resolvconf service doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1536181/+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 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast
Do you have the "dnsmasq" package installed and is the instance of the dnsmasq program started by the "dnsmasq" package configured to listen at 127.0.1.1? -- 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/1534501 Title: [URGENT] dnsmasq errors fills up syslogs extremely fast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1534501/+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 1534501] Re: [URGENT] dnsmasq errors fills up syslogs extremely fast
First, it appears that NetworkManager doesn't handle the error well and retries without sleeping. Needs fixing. Separate issue: Why is the error occurring on your machine? Why do you get "dnsmasq[30613]: failed to create listening socket for 127.0.1.1: Address already in use"? -- 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/1534501 Title: [URGENT] dnsmasq errors fills up syslogs extremely fast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1534501/+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 1516329] Re: DNS BUG delay resolution of LAN DNS
** Package changed: resolvconf (Ubuntu) => dnsmasq (Ubuntu) -- 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/1516329 Title: DNS BUG delay resolution of LAN DNS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1516329/+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 1501189] Re: DNS breaks when port=0 is used in dnsmasq.conf
*** This bug is a duplicate of bug 1042275 *** https://bugs.launchpad.net/bugs/1042275 ** This bug has been marked a duplicate of bug 1042275 Please enhance dnsmasq to talk directly to resolvconf and to register only its actual listening address(es) -- 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/1501189 Title: DNS breaks when port=0 is used in dnsmasq.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1501189/+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 1485316] Re: dnsmasq breaks DNS, if not used as DNS server
Best to submit this wish to the Debian bug tracking system so that Debian will also benefit from this enhancement. -- 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/1485316 Title: dnsmasq breaks DNS, if not used as DNS server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1485316/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Christian, the workaround is to comment out the line dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf. -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1466608] Re: Unable to resolve domains with large EDNS0 replies
To add that, or any other, option to resolv.conf permanently, add the line options edns0 to the file /etc/resolvconf/resolv.conf.d/base and then resolvconf will include it in the resolv.conf that it generates. ** Changed in: dnsmasq (Ubuntu) Status: New = 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/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+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 1466608] Re: Unable to resolve domains with large EDNS0 replies
Hi. I don't see how resolvconf could be responsible for this problem. Initial observation: it seems that dig gets the correct answer from dnsmasq when it supplies the additional option udp:1280, but the glibc resolver doesn't get the right answer from dnsmasq when it fails to supply that option. Reassigning to dnsmasq. ** Package changed: resolvconf (Ubuntu) = dnsmasq (Ubuntu) -- 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/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
** Changed in: network-manager (Ubuntu) Status: In Progress = New -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1449083] Re: dnsmasq reverses order of dns servers
Dnsmasq treats all nameservers as equivalent (except insofar as it is instructed to use particular nameservers to resolve names in particular domains). The C library resolver, on the other hand, tries one nameserver at a time in the order that their addresses are listed in resolv.conf. If you must try the nameservers in a particular order then don't use dnsmasq on the local machine. If you are using NetworkManager which by default starts a slave dnsmasq instance to serve as a local forwarding nameserver then with root privileges edit /etc/NetworkManager/NetworkManager.conf to comment out the line `dns=dnsmasq` (by putting a `#` at the beginning of the line) and then restart the machine. ** 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/1449083 Title: dnsmasq reverses order of dns servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1449083/+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 1313392] Re: dnsmasq crashes dhcp/internet connection and uses a lot of cpu
*** This bug is a duplicate of bug 1314697 *** https://bugs.launchpad.net/bugs/1314697 ** This bug has been marked a duplicate of bug 1314697 DNS resolution no longer works; dnsmasq uses 100% CPU -- 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/1313392 Title: dnsmasq crashes dhcp/internet connection and uses a lot of cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1313392/+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 1416895] Re: /etc/dnsmasq.conf does not contain an ending newline character
Confirmed that the bug affects 2.72-2. $ cat /etc/dnsmasq.conf | tail -n 2 # Include all files in a directory which end in .conf #conf-dir=/etc/dnsmasq.d/*.conf$ od -t c /etc/dnsmasq.conf | tail -n 2 0062620 / * . c o n f 0062627 $ ** Changed in: dnsmasq (Ubuntu) Status: New = Confirmed -- 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/1416895 Title: /etc/dnsmasq.conf does not contain an ending newline character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1416895/+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 1416895] Re: /etc/dnsmasq.conf does not contain an ending newline character
Just checked 2.72-1 and it doesn't seem to have this problem. $ cat /etc/dnsmasq.conf | tail -n 2 #conf-file=/etc/dnsmasq.more.conf #conf-dir=/etc/dnsmasq.d $ od -t c /etc/dnsmasq.conf | tail -n 2 0062320 / e t c / d n s m a s q . d \n 0062337 -- 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/1416895 Title: /etc/dnsmasq.conf does not contain an ending newline character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1416895/+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 1414887] Re: dns query from localnetwork ignored
First, as suggested by the author of dnsmasq, the `local-service` should be in the default configuration. However, Ubuntu 14.10 doesn't have that What the man page exactly says is that local-service only has effect i[f] there are no --interface --except-interface, --listen-address or --auth-server options. Here is what I found out how dnsmasq is started in Ubuntu 14.10: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 [...] This is not the dnsmasq process started by the dnsmasq package. It is the local forwarding dnsmasq process started by NetworkManager. If your complaint is that the local forwarding dnsmasq process started by NetworkManager doesn't respond to queries coming from the network then the answer is that this process is not supposed to do that. But I don't think that this is your complaint because you said that you didn't have the problem in Ubuntu 13.10. On my machine, the dnsmasq process started by the dnsmasq package looks like this in ps -elf output /usr/sbin/dnsmasq -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq -r /var/run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old ,.dpkg-new --local-service As no --interface --except-interface, --listen-address or --auth-server option is given, the --local-service option is active. In order to deactivate the local-service feature, I suggest you configure dnsmasq with one of the above mentioned options. ** 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/1414887 Title: dns query from localnetwork ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1414887/+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 1414887] Re: dns query from localnetwork are blocked
Ubuntu 13.10 (Saucy) included dnsmasq 2.66 or so. In dnsmasq 2.69 an important change was made which may be the cause of your problem. This change affects Ubuntu 14.10 and later, but not Ubuntu 14.04LTS (Trusty) which shipped with dnsmasq 2.68-1. The change is mentioned in the changelog (quoted below) and it should be obvious how this might be affecting you. Read the new dnsmasq manpage for a longer description of the local-service option. dnsmasq (2.69-1) unstable; urgency=low * New upstream. * Set --local-service. (closes: #732610) This tells dnsmasq to ignore DNS requests that don't come from a local network. It's automatically ignored if --interface --except-interface, --listen-address or --auth-server exist in the configuration, so for most installations, it will have no effect, but for otherwise-unconfigured installations, it stops dnsmasq from being vulnerable to DNS-reflection attacks. -- Simon Kelley si...@thekelleys.org.uk Tue, 4 Feb 2014 16:28:12 + ** 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/1414887 Title: dns query from localnetwork are blocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1414887/+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 978356] Re: squid3 gets killed at startup with dnsmasq
** Summary changed: - squid3 gets killed at startup with dnsmasq and no networkmanager + squid3 gets killed at startup with 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/978356 Title: squid3 gets killed at startup with dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/978356/+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 1284607] Re: resolvconf ignores given dns-servers in /etc/network/interfaces
Is dnsmasq getting its DNS server information from resolvconf, which in turn gets it from /etc/network/interfaces? Or, does dnsmasq take what it likes from /etc/network/interfaces directly, discarding the rest? 1. If you have only the dnsmasq-base and network-manager packages installed then a dnsmasq process is run as a slave of NetworkManager and gets its nameserver information exclusively from NetworkManager. This dnsmasq process provides name service exclusively at IP address 127.0.1.1. 2. If you have the dnsmasq package installed then a(nother) dnsmasq process is run independently of NetworkManager. By default this independent dnsmasq service is configured to obtain its nameserver information exclusively from resolvconf which in turn gets nameserver information from interface configuration processes including ifup, whose configuration file is /etc/network/interfaces. The fact that you have no /etc/dnsmasq.conf strongly suggests that you do not have the dnsmasq package installed and so you fall into class #1. Dnsmasq itself never looks in /etc/network/interfaces. To understand how resolvconf works, please consult /usr/share/doc/resolvconf/README.gz . To understand how Ubuntu uses NetworkManager, dnsmasq and resolvconf, please consult https://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/ . ** Changed in: dnsmasq (Ubuntu) Status: New = 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/1284607 Title: resolvconf ignores given dns-servers in /etc/network/interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1284607/+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 1384394] Re: /etc/network/interfaces: dns-nameservers entries for bridge br* interfaces are ignored i.e. they are not listed in /etc/resolv.conf when invoking ifup command
I gather that you want to use the fact that the resolver happens to try one address after another, in the order that they are listed in resolv.conf, as a way of giving precedence of one domain name system (the service provided over the br* interfaces) over another domain name system (the one serving the Internet and accessible by the forwarder on your machine at 127.0.1.1). That's not how DNS or the resolver were meant to be used and hence that is not implemented by the default system configuration. Given your aims, it's up to you to configure /etc/resolvconf/interface-order so that br* is listed before lo*. -- 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/1384394 Title: /etc/network/interfaces: dns-nameservers entries for bridge br* interfaces are ignored i.e. they are not listed in /etc/resolv.conf when invoking ifup command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1384394/+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 1363366] Re: DNSSEC for dnsmasq
** Description changed: This is a wishlist item. - I'd like to use DNSSEC for dnsmasq out of the box. Currently support for - DNSSEC appears to be disabled at compile time: if I add dnssec options - to the dnsmasq.conf, it doesn't accept the configuration. I'm using - Ubuntu Trusty. + I'd like to turn on dnsmasq's DNSSEC validation. However, it appears + that support for DNSSEC is disabled at compile time: if I add the + dnssec option to the dnsmasq.conf, dnsmasq doesn't accept the + configuration. I'm using Ubuntu Trusty. - As a workaround, I currently configured DNSSEC to proxy via upstream DNS - with the proxy-dnssec option -- but this is insecure. + As a workaround, I currently configure dnsmasq to rely on the DNSSEC + validation of upstream DNS servers (i.e., I use the proxy-dnssec + option) but this is not entirely secure. -- 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/1363366 Title: DNSSEC for dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1363366/+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 1363366] Re: DNSSEC for dnsmasq
Trusty has dnsmasq 2.68-1. Looking at the buildlog I don't see HAVE_DNSSEC being defined on the compiler command line. gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -W -DHAVE_DBUS -DHAVE_CONNTRACK -DLOCALEDIR='/usr/share/locale' -DVERSION='2.68' -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -c dnsmasq.c However, in the build log of dnsmasq 2.71-1, which is in Utopic, I do see HAVE_DNSSEC being defined on the compiler command line. gcc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -W -DNO_NETTLE_ECC -DHAVE_DBUS -DHAVE_CONNTRACK -DHAVE_DNSSEC -DLOCALEDIR='/usr/share/locale' -DVERSION='2.71' -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -c dnsmasq.c I surmise, therefore, that this wish is fulfilled in Utopic. -- 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/1363366 Title: DNSSEC for dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1363366/+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 1320127] Re: high use of resource
*** This bug is a duplicate of bug 1314697 *** https://bugs.launchpad.net/bugs/1314697 ** This bug is no longer a duplicate of bug 1313393 dnsmasq lockup at 100% cpu ** This bug has been marked a duplicate of bug 1314697 DNS resolution no longer works; dnsmasq uses 100% CPU -- 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/1320127 Title: high use of resource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1320127/+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 1313393] Re: dnsmasq lockup at 100% cpu
*** This bug is a duplicate of bug 1314697 *** https://bugs.launchpad.net/bugs/1314697 ** This bug has been marked a duplicate of bug 1314697 DNS resolution no longer works; dnsmasq uses 100% CPU -- 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/1313393 Title: dnsmasq lockup at 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1313393/+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 1315741] Re: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed
Fixed in Debian dnsmasq 2.71-1 ** Changed in: dnsmasq (Ubuntu) Status: Confirmed = Fix Released -- 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/1315741 Title: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1315741/+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 1315741] Re: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed
Fixed in Utopic -- 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/1315741 Title: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1315741/+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 1319536] Re: No internet after install
*** This bug is a duplicate of bug 1314697 *** https://bugs.launchpad.net/bugs/1314697 ** This bug has been marked a duplicate of bug 1314697 DNS resolution no longer works; dnsmasq uses 100% CPU -- 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/1319536 Title: No internet after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1319536/+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 1314697] Re: Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU
** Summary changed: - Upon upgrade, DNS resolution no longer works + Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU -- 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/1314697 Title: Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+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 1317444] Re: dnsmasq spins at 100% cpu trying to receive socket messages via stdin
*** This bug is a duplicate of bug 1314697 *** https://bugs.launchpad.net/bugs/1314697 ** This bug has been marked a duplicate of bug 1314697 Upon upgrade, DNS resolution no longer works; dnsmasq uses 100% CPU -- 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/1317444 Title: dnsmasq spins at 100% cpu trying to receive socket messages via stdin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1317444/+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 1315741] Re: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed
The Debian dnsmasq maintainer reports that he has uploaded a new version of the package for Debian. This will need to be pushed over to Ubuntu when it's available. -- 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/1315741 Title: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1315741/+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 1315741] Re: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed
the script fails to look at the return value I was wrong; the script does look at the return value. ** Package changed: resolvconf (Ubuntu) = dnsmasq (Ubuntu) ** Also affects: dnsmasq Importance: Undecided Status: New ** No longer affects: dnsmasq ** Also affects: dnsmasq (Debian) Importance: Undecided Status: New -- 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/1315741 Title: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1315741/+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 1315741] Re: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed
** Bug watch added: Debian Bug tracker #746941 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746941 ** Changed in: dnsmasq (Debian) Importance: Undecided = Unknown ** Changed in: dnsmasq (Debian) Status: New = Unknown ** Changed in: dnsmasq (Debian) Remote watch: None = Debian Bug tracker #746941 -- 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/1315741 Title: The dnsmasq initscript fails to disable itself when the dnsmasq package is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1315741/+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 1314697] Re: Upon upgrade, DNS resolution no longer works
Assuming you are using NetworkManager, a better way to work around the problem than editing resolv.conf by hand is to edit /etc/NetworkManager/NetworkManager.conf and comment out the line `dns=dnsmasq`, save, and then `restart network-manager`. This will cause NetworkManager not to use a slave instance of dnsmasq as a local forwarding nameserver. -- 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/1314697 Title: Upon upgrade, DNS resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+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 1294239] Re: dnsmasq preventing DNS lookup with firepass sslvpn
Make sure that the resolvconf package is installed and that /etc/resolv.conf is a symbolic link to ../run/resolvconf/resolv.conf and that the proprietary software on your Linux Mint system doesn't futz with /etc/resolv.conf. ** 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/1294239 Title: dnsmasq preventing DNS lookup with firepass sslvpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1294239/+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 1294239] Re: dnsmasq preventing DNS lookup with firepass sslvpn
Can you please edit the bug description to give a lot more detail about your system and about the malfunction? -- 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/1294239 Title: dnsmasq preventing DNS lookup with firepass sslvpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1294239/+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 1294239] Re: dnsmasq preventing DNS lookup with firepass sslvpn
Comment out the line `dns=dnsmasq` in /etc/NetworkManager/NetworkManager.conf and reboot. ** 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/1294239 Title: dnsmasq preventing DNS lookup with firepass sslvpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1294239/+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 1247803] Re: dnsmasq temporarily breaks DNS resolution when starting for the first time
We certainly don't want to run resolvconf -u too few times. That is the bug. It causes no logical malfunction to run resolvconf -u too many times, but doing so is not efficient. When a resolvconf update occurs then all the scripts in /etc/resolvconf/update.d/ get run. If a heavy update script is present (one that copies files, reconfigures things and/or restarts services, etc.) then the update can take a significant amount of time. In that case it's bad to do an extra, unnecessary update. And I think it's ugly to do two updates in a row if one is sufficient. The proposed conditional only suppresses running resolvconf -u if ENABLED=1 and resolvconf is not being used (ie IGNORE_RESOLVCONF=yes). Is this really such a common case that adding complexity to get the minor optimization of not running resolvconf -u is worth it? You have a point there. Perhaps it is, perhaps it is not worth the added code complexity in the postinst. The maintainer will be the judge. Also, doesn't your argument about ENABLED=0 later being changed to ENABLED=1 also apply to IGNORE_RESOLVCONF=yes later being changed to IGNORE_RESOLVCONF=no? No, I don't think it applies. In the ENABLED=0 case, resolvconf doesn't get run by the dnsmasq initscript. So unless the postinst does resolvconf -u there is nothing to ensure that if dnsmasq is later restarted with ENABLED=1 and IGNORE_RESOLVCONF=no then /var/run/dnsmasq/resolv.conf will have been written. In the ENABLED=1 IGNORE_RESOLVCONF=yes case resolvconf does get run in the dnsmasq initscript and /var/run/dnsmasq/resolv.conf gets written (even though it won't be used). So if dnsmasq is later restarted with ENABLED=1 and IGNORE_RESOLVCONF=no then /var/run/dnsmasq/resolv.conf is ready. -- 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/1247803 Title: dnsmasq temporarily breaks DNS resolution when starting for the first time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1247803/+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 1247803] Re: dnsmasq temporarily breaks DNS resolution when starting for the first time
Hmm, good questions . /me thinks. The (small) gain is that we omit an unneeded update run prior to the update run that occurs shortly afterwards when the dnsmasq initscript calls resolvconf. When other things touch resolvconf the update run can't be omitted. We don't want to skip the update run when ENABLED=0 because in that case the initscript itself does not instigate an update run. If no update run is instigated either in the postinst or in the initscript, and the admin later sets ENABLED=1 and IGNORE_RESOLVCONF=no and does /etc/init.d/dnsmasq start and nothing else has instigated an update run in the meantime then dnsmasq starts with an out-of-date /var/run/dnsmasq/resolv.conf which is what we are trying to avoid. So when ENABLED=0 the update run must be done in the postinst even if IGNORE_RESOLVCONF is set. The code should thus look like this: # # If ENABLED=0 then the initscript does not call resolvconf, so we do an # update run here in order to ensure that /var/run/dnsmasq/resolv.conf # is up to date should dnsmasq later be started (with ENABLED=1). # # If ENABLED=1 then the initscript will call resolvconf and thus instigate an # update run, thus updating /var/run/dnsmasq/resolv.conf; but, unless # IGNORE_RESOLVCONF is yes, we have to do an update run here so that # /var/run/dnsmasq/resolv.conf is valid before dnsmasq starts. # if [ $ENABLED = 0 ] || [ $IGNORE_RESOLVCONF != yes ] ; then resolvconf -u fi -- 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/1247803 Title: dnsmasq temporarily breaks DNS resolution when starting for the first time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1247803/+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 1247803] Re: dnsmasq temporarily breaks DNS resolution when starting for the first time
When the dnsmasq package is installed its postinst starts the dnsmasq daemon via the initscript. Dnsmasq initially reads what is most probably an empty file from /var/run/dnsmasq/resolv.conf and so initially can't resolve names. (The file is probably empty because it is generated by /etc/resolvconf/update.d/dnsmasq which is included in the dnsmasq package.) Then the dnsmasq initscript tells resolvconf that dnsmasq is listening at 127.0.0.1. In response to this, resolvconf runs the aforementioned hook script /etc/resolvconf/update.d/dnsmasq which writes a new /var/run/dnsmasq/resolv.conf containing information about other nameservers. The dnsmasq binary notices that the latter file has changed and re-reads it. Meanwhile resolvconf updates /etc/resolv.conf to contain nameserver 127.0.0.1 so that the resolver will talk to dnsmasq. It's this meanwhile that is the problem. Resolvconf may update resolv.conf to point to dnsmasq before dnsmasq is ready to resolve names on the basis of the information just written to /var/run/dnsmasq/resolv.conf. In other words, you're right. :) I think that the postinst should be enhanced such that if /etc/resolvconf/update.d/dnsmasq has appeared or changed on install or upgrade then it (the postinst) does resolvconf -u before starting dnsmasq. The postinst should refrain from doing the resolvconf -u if IGNORE_RESOLVCONF is set in /etc/default/dnsmasq. ** Changed in: dnsmasq (Ubuntu) Status: New = Confirmed ** Also affects: dnsmasq (Debian) Importance: Undecided Status: New -- 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/1247803 Title: dnsmasq temporarily breaks DNS resolution when starting for the first time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1247803/+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 1234132] Re: dnsmasq needs to trigger mountall rescan of network mounts
** Description changed: - When using DNS resolving daemons like dnsmasq the mountall-net is done - to early in the boot process when DNS is not available. + When using a DNS resolving daemon such as dnsmasq the mountall-net is + done too early in the boot process, when DNS is not available. -- 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/1234132 Title: dnsmasq needs to trigger mountall rescan of network mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1234132/+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 1203430] Re: dnsmasq doesn't listen on a given 127.* listen-address if bind-dynamic, interface and except-interface options are given
Fixed in 2.67, not in 2.66. -- 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/1203430 Title: dnsmasq doesn't listen on a given 127.* listen-address if bind- dynamic, interface and except-interface options are given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1203430/+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 1229023] Re: Nameservers are not setup correctly
Dnsmasq gets its nameserver addresses from resolvconf via the file /var/run/dnsmasq/resolv.conf. That /etc/resolv.conf contains only 127.0.0.1 is correct. ** Changed in: dnsmasq (Ubuntu) Status: New = 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/1229023 Title: Nameservers are not setup correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1229023/+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 1229023] Re: Nameservers are not setup correctly
You don't need to set `listen-address=127.0.0.1` in /etc/dnsmasq.conf; dnsmasq listens on that address by default. If dnsmasq is not being used then you have a nonstandard configuration. If you do not need a nonstandard configuration then I suggest that you purge the dnsmasq package and reinstall it. -- 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/1229023 Title: Nameservers are not setup correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1229023/+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 1228955] Re: dnsmasq changeds virtualbox guests PTR queries into A queries
How do you rule out this being VirtualBox's fault? -- 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/1228955 Title: dnsmasq changeds virtualbox guests PTR queries into A queries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1228955/+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 1228955] Re: dnsmasq changeds virtualbox guests PTR queries into A queries
Hi Bar, I can reproduce the behavior: Debian 7 in VM with NATted network interface on VirtualBox 4.2.16 on Ubuntu 13.04 with the NetworkManager- controlled dnsmasq instance running. Using wireshark on the host I see 127.0.1.1 receiving an A query instead of a PTR query. ** Package changed: dnsmasq (Ubuntu) = virtualbox (Ubuntu) -- 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/1228955 Title: dnsmasq changeds virtualbox guests PTR queries into A queries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1228955/+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 1172467] Re: Dnsmasq caches negative results if it starts before the network is up
Jérôme, it's nice to hear that it is working correctly, but which of the following is the case? 1. Dnsmasq is working correctly in the standard factory configuration. 2. It is working with no-negcache mode activated. 3. It is working with clear-on-reload mode activated. 4. It is working and the circumstances under which the problem occurs haven't presented themselves again. -- 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/1172467 Title: Dnsmasq caches negative results if it starts before the network is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1172467/+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 1172467] Re: Dnsmasq caches negative results if it starts before the network is up
Jérôme, can you please see if clear-on-reload fixes the problem, without no-negcache? ** 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/1172467 Title: Dnsmasq caches negative results if it starts before the network is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1172467/+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 1203430] Re: dnsmasq doesn't listen on a given 127.* listen-address if bind-dynamic, interface and except-interface options are given
** Changed in: dnsmasq (Ubuntu) Status: New = In Progress -- 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/1203430 Title: dnsmasq doesn't listen on a given 127.* listen-address if bind- dynamic, interface and except-interface options are given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1203430/+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 1172467] Re: Dnsmasq caches negative results if it starts before the network is up
Hi Simon, I think we've established that the submitter is having a problem with dnsmasq server, not with NetworkManager-controlled dnsmasq. So it would be interesting to know if clear-on-reload fixes the submitter's problem. (He already said that no-negcache fixes it.) That clear-on-reload is ignored in the D-Bus case sounds like a distinct issue. What about Stéphane's suggestion that dnsmasq treats failure to find a name in /etc/hosts as a NXDOMAIN? -- 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/1172467 Title: Dnsmasq caches negative results if it starts before the network is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1172467/+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 1203430] [NEW] dnsmasq doesn't listen on a given 127.* listen-address if bind-dynamic, interface and except-interface options are given
Public bug reported: If I start dnsmasq as follows dnsmasq --conf-file= --resolv-file=/tmp/r.conf --bind-dynamic --listen-address=127.0.3.1 echo nameserver 192.168.1.254 /tmp/r.conf then I can resolve a name, e.g., www.microsoft.com, with dig. dig @127.0.3.1 www.microsoft.com And I can still resolve names with that dig command if I start dnsmasq as follows (with --interface=eth0). dnsmasq --conf-file= --resolv-file=/tmp/r.conf --bind-dynamic --listen-address=127.0.3.1 --interface=eth0 echo nameserver 192.168.1.254 /tmp/r.conf However, I can't resolve anything if I start dnsmasq as follows (with --except-interface=lo). dnsmasq --conf-file= --resolv-file=/tmp/r.conf --bind-dynamic --listen-address=127.0.3.1 --interface=eth0 --except-interface=lo echo nameserver 192.168.1.254 /tmp/r.conf Dnsmasq just doesn't respond even though it's supposedly listening at 127.0.3.1. # netstat -nlp | grep :53 tcp0 0 127.0.3.1:530.0.0.0:* LISTEN 5887/dnsmasq tcp0 0 192.168.1.20:53 0.0.0.0:* LISTEN 5887/dnsmasq tcp6 0 0 fe80::f2de:f1ff:fe6b:53 :::*LISTEN 5887/dnsmasq udp0 0 0.0.0.0:53530.0.0.0:* 768/avahi-daemon: r udp0 0 127.0.3.1:530.0.0.0:* 5887/dnsmasq udp0 0 192.168.1.20:53 0.0.0.0:* 5887/dnsmasq udp6 0 0 :::5353 :::* 768/avahi-daemon: r udp6 0 0 fe80::f2de:f1ff:fe6b:53 :::* 5887/dnsmasq If I start dnsmasq as above but with --bind-interfaces instead of --bind-dynamic then the dig command works. Additional info: # ifconfig eth0 Link encap:Ethernet HWaddr f0:de:f1:6b:22:bf inet addr:192.168.1.20 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::f2de:f1ff:fe6b:22bf/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:124343 errors:0 dropped:0 overruns:0 frame:0 TX packets:59204 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:56834893 (56.8 MB) TX bytes:8614172 (8.6 MB) Interrupt:20 Memory:f250-f252 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:806 errors:0 dropped:0 overruns:0 frame:0 TX packets:806 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:220819 (220.8 KB) TX bytes:220819 (220.8 KB) Dnsmasq version: 2.65-1ubuntu1 ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New -- 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/1203430 Title: dnsmasq doesn't listen on a given 127.* listen-address if bind- dynamic, interface and except-interface options are given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1203430/+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 1163147] Re: can't resolve lan hosts (regression)
** Description changed: First, apologies for the complicated configuration. I use the 'uvt' front-end to libvirt-managed kvm guest machines. I also have a LAN with a router that does local dynamic DNS configuration with the client-provided dhcp hostnames. I would like to resolve hostnames on my machine for both VM guests and LAN hosts. This configuration worked for 12.04 LTS, 12.10, but does not work for Raring. I have followed the directions at https://wiki.ubuntu.com/SecurityTeam/TestingEnvironment#Networking_with_libvirt : Put a line into /etc/dhcp/dhclient.conf like so: - + prepend domain-name-servers 192.168.122.1; - + Disable the system dnsmasq to prevent it from looping with libvirt's dnsmasq by modifying /etc/NetworkManager/NetworkManager.conf to comment out the following line: - + #dns=dnsmasq My /etc/resolv.conf when the wireless is up: $ cat /etc/resolv.conf # 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 192.168.122.1 nameserver 192.168.1.1 Here's trying to look up a host on my network: + $ host dean Host dean not found: 3(NXDOMAIN) $ host dean 192.168.122.1 Using domain server: Name: 192.168.122.1 Address: 192.168.122.1#53 - Aliases: + Aliases: Host dean not found: 3(NXDOMAIN) $ host dean 192.168.1.1 Using domain server: Name: 192.168.1.1 Address: 192.168.1.1#53 - Aliases: + Aliases: dean has address 192.168.1.236 - $ + $ $ host 192.168.1.236 236.1.168.192.in-addr.arpa domain name pointer dean. $ host 192.168.1.236 192.168.122.1 Using domain server: Name: 192.168.122.1 Address: 192.168.122.1#53 - Aliases: + Aliases: 236.1.168.192.in-addr.arpa domain name pointer dean. $ host 192.168.1.236 192.168.1.1 Using domain server: Name: 192.168.1.1 Address: 192.168.1.1#53 - Aliases: + Aliases: 236.1.168.192.in-addr.arpa domain name pointer dean. - $ - - I want $ host dean - Host dean not found: 3(NXDOMAIN) - $ host dean 192.168.122.1 - Using domain server: - Name: 192.168.122.1 - Address: 192.168.122.1#53 - Aliases: - - Host dean not found: 3(NXDOMAIN) - $ host dean 192.168.1.1 - Using domain server: - Name: 192.168.1.1 - Address: 192.168.1.1#53 - Aliases: - - dean has address 192.168.1.236 - $ - $ host 192.168.1.236 - 236.1.168.192.in-addr.arpa domain name pointer dean. - $ host 192.168.1.236 192.168.122.1 - Using domain server: - Name: 192.168.122.1 - Address: 192.168.122.1#53 - Aliases: - - 236.1.168.192.in-addr.arpa domain name pointer dean. - $ host 192.168.1.236 192.168.1.1 - Using domain server: - Name: 192.168.1.1 - Address: 192.168.1.1#53 - Aliases: - - 236.1.168.192.in-addr.arpa domain name pointer dean. - $ - + $ I'm surprised that 192.168.122.1 knows the reverse information for dean. I want the query for plain dean to succeed. (As that's how 'ssh' works..) If I swap the order of the lines in /etc/resolv.conf to put 192.168.1.1 first, I get the opposite situation: $ host dean dean has address 192.168.1.236 $ uvt start sec-precise-amd64 Sleeping 5 seconds to give 'sec-precise-amd64' a chance to start $ ssh sec-precise-amd64 echo hello ssh: Could not resolve hostname sec-precise-amd64: No such file or directory $ ssh sec-precise-amd64. echo hello ssh: Could not resolve hostname sec-precise-amd64.: No such file or directory $ ssh sec-precise-amd64.local echo hello hello - I do not want to use the .local form for all my VMs. That is annoying and the scripts we have written around uvt assume that the .local is not necessary. 12.04 LTS and 12.10 had this working well. I would like Raring to work that well again. Thanks ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 00:04:49 2013 InstallationDate: Installed on 2012-10-18 (166 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: - TERM=rxvt-unicode - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=rxvt-unicode + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to raring on 2013-03-18 (15 days ago) -- 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com
[Bug 1163147] Re: can't resolve lan hosts (regression)
Hi Seth, Just read your bug report again. It appears that you have two nameservers, neither of which has complete DNS information. You need to configure things such that each nameserver listed in resolv.conf can resolve all names you want resolved. On a LAN, for example, there is sometimes a nameserver that resolves names in a TLD such as .private. Such a nameserver has to be so configured that it *also* resolves Internet DNS names. Likewise in your setup. P.S. Can you please edit your description to say which machine has which IP address? And provide more details about how you have configured your nameservers? -- 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+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 995332] Re: Validate DNSSEC by default
** Changed in: dnsmasq (Ubuntu) Status: Triaged = Invalid ** Summary changed: - Validate DNSSEC by default + Please enhance NetworkManager such that DNSSEC validation is done whenever possible -- 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/995332 Title: Please enhance NetworkManager such that DNSSEC validation is done whenever possible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/995332/+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 1042275] Re: Please enhance dnsmasq to talk directly to resolvconf and to register only its actual listening address(es)
** Summary changed: - dnsmasq should not register 127.0.0.1 with resolvconf if it's not listening on lo + Please enhance dnsmasq to talk directly to resolvconf and to register only its actual listening address(es) -- 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/1042275 Title: Please enhance dnsmasq to talk directly to resolvconf and to register only its actual listening address(es) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1042275/+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 661599] Re: Please include the dnsmasq package on the Server ISO
The dnsmasq package is still not included on the Server ISO in 13.04. The dnsmasq package is about 15KiB in size. ** Summary changed: - The dnsmasq package isn't available on the server ISO + Please include the dnsmasq package on the Server ISO -- 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/661599 Title: Please include the dnsmasq package on the Server ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/661599/+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 661599] Re: Please include the dnsmasq package on the Server ISO
** Package changed: dnsmasq (Ubuntu) = ubuntu-meta (Ubuntu) -- 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/661599 Title: Please include the dnsmasq package on the Server ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/661599/+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 1172467] Re: NetworkManager uses dnsmasq with negative DNS cache enabled
** Package changed: network-manager (Ubuntu) = dnsmasq (Ubuntu) ** Summary changed: - NetworkManager uses dnsmasq with negative DNS cache enabled + Dnsmasq caches negative results if it starts before the network is up -- 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/1172467 Title: Dnsmasq caches negative results if it starts before the network is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1172467/+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 1172467] Re: Dnsmasq caches negative results if it starts before the network is up
Stéphane wrote: Can you confirm that you have the dnsmasq package installed and not only dnsmasq-base? If so, then that bug is invalid as when you install dnsmasq on your system, that'll bypass NetworkManager's own instance and so will run with the default dnsmasq settings (including caching). I don't fully understand what you say here. 1. If the dnsmasq package is installed alongside network-manager then the dnsmasq server instance will not bypass NM's instance but will forward queries to it. 2. But that's not the main issue. This report seems to be that dnsmasq caches failed lookups as if they were NXDOMAINs. If that's true then it could be regarded as a bug in dnsmasq. You are right that this in no way implies a bug in NM. -- 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/1172467 Title: Dnsmasq caches negative results if it starts before the network is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1172467/+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 1172467] Re: Dnsmasq caches negative results if it starts before the network is up
What do you think, Simon? ** Changed in: dnsmasq (Ubuntu) Status: Incomplete = New -- 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/1172467 Title: Dnsmasq caches negative results if it starts before the network is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1172467/+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 1163147] Re: can't resolve lan hosts (regression)
You need to configure things such that each nameserver listed in resolv.conf can resolve all names you want resolved. This requirement feels impossible to meet; the dnsmasq spawned by libvirt on my laptop knows only the VMs running on my laptop. It is not possible for this dnsmasq to know the hosts on my LAN That instance of dnsmasq, call it DV, provides services to VMs. If the VMs are going to access the LAN or the Internet then DV needs to forward DNS queries for which it isn't authoritative to a nameserver on the LAN or on the Internet. I have a standard consumer router on my network to provide DHCP and dynamic DNS services. I do not want to require my laptop to be on and connected to my LAN for other hosts to continue using the LAN. Agreed. Your laptop should ultimately send DNS queries to the nameserver on the router, just as any other machine on the LAN does. You want to be able to resolve VM names on your laptop as well as LAN and Internet names. In that case you will have to use DV as your laptop's nameserver and configure DV to forward DNS queries to the router and not use the nameserver that the laptop is using (which is DV itself — that would be a loop). This should be implemented cleanly using resolvconf. Here is an outline of how that should be done, blindly assuming a few things such as that the dnsmasq package is not installed on your machine. I blindly assume, that is, that libvirt runs an instance of dnsmasq using the binary in the dnsmasq-base package. Basically, DV should behave similarly to how the server instance of dnsmasq (from the dnsmasq package) behaves with respect to resolvconf. 1. DV should register with resolvconf a loopback address at which it listens. Configure it to listen at 127.0.0.1 on the laptop and modify its control script to run echo nameserver 127.0.0.1 | resolvconf -a lo.dnsmasq on start and resolvconf -d lo.dnsmasq on stop. 2. DV should have a hook script in /etc/resolvconf/update.d/ which generates a list of forwarders for DV to use. The resolvconf hook script from the dnsmasq package can be used verbatim for this purpose; simply put the file in update.d/ and configure DV to use /var/run/dnsmasq/resolv.conf as its only forwarders-list file. If you want details I can help you, or you can follow the good example of the dnsmasq package. ** Summary changed: - can't resolve lan hosts (regression) + Can't resolve both VM names and LAN names -- 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/1163147 Title: Please run dnsmasq in such a way that it can also be used on the host — to look up the VMs' names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1163147/+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 1163147] Re: Can't resolve both VM names and LAN names
I think that this is ultimately an enhancement request for libvirt. ** Package changed: dnsmasq (Ubuntu) = libvirt (Ubuntu) ** Changed in: libvirt (Ubuntu) Status: Incomplete = New ** Summary changed: - Can't resolve both VM names and LAN names + Please run dnsmasq in such a way that it can also be used on the host — to look up the VMs' names -- 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/1163147 Title: Please run dnsmasq in such a way that it can also be used on the host — to look up the VMs' names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1163147/+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 1091602] Re: Please enhance bind9 to use forwarder addresses from resolvconf
The feature was dropped from the resolvconf package in Ubuntu 13.04. The bind9 maintainers have been invited to add a similar feature to support BIND 9. Your contribution may help to convince them to take action. Until this feature actually appears in bind9 you will have to implement it locally if you want it. Make sure you rename the file to something like `/etc/resolvconf/update.d/mybind` so that it will not be removed by the resolvconf package on a subsequent upgrade. ** No longer affects: resolvconf (Debian) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1091602 Title: Please enhance bind9 to use forwarder addresses from resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1091602/+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: domain name completion broken when dnsmasq is used
** Changed in: dnsmasq (Ubuntu) Status: Expired = Confirmed ** Description changed: - dnsmasq does not resolve DNS names correcty. + Dnsmasq sometimes 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, + 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) -- 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: domain name completion broken when dnsmasq is used
Arno, Does disabling NetworkManager-controlled dnsmasq fix the problem? (To disable NetworkManager-controlled dnsmasq, comment out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and then restart network- manager.) Hypothesis: dnsmasq is given two nameserver addresses. The first nameserver listed, which is the one always consulted first if dnsmasq is not used, functions correctly. The second one malfunctions. Dnsmasq sometimes consults the second one and therefore sometimes returns incorrect results. -- 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 1163147] Re: can't resolve lan hosts (regression)
** This bug is no longer a duplicate of bug 1126488 libvirt instance of dnsmasq in raring fails to forward DNS requests -- 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+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 1163147] Re: can't resolve lan hosts (regression)
For the record, please say which version of the uvt script you are using. In the description you say: This configuration worked for 12.04 LTS, 12.10, but does not work for Raring. In comment #6 you say: I don't think this is a duplicate of bug #1126488 since I made the conscious decision to _not_ upgrade to Raring Can you be more clear about whether you are running 12.04 or Raring or some combination of the two? In the latter case, which packages have you upgraded to Raring? ** 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+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 1163147] Re: can't resolve lan hosts (regression)
*** This bug is a duplicate of bug 1126488 *** https://bugs.launchpad.net/bugs/1126488 ** This bug has been marked a duplicate of bug 1126488 libvirt instance of dnsmasq in raring fails to forward DNS requests -- 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+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 1163147] Re: can't resolve lan hosts (regression)
Put a line into /etc/dhcp/dhclient.conf like so: prepend domain-name-servers 192.168.122.1; The following doesn't address the main issue but does seem to me to be worth mentioning. Since the introduction of resolvconf in Ubuntu 12.04 it is more advisable to configure nameserver addresses via the network configuration tool, i.e., either ifup or NetworkManager. If you are using ifup then you add extra nameserver addresses to logical interface definitions in /etc/network/interfaces as arguments to the dns-nameservers option. If you are using NetworkManager (as you seem to be doing, given that you are editing NetworkManager.conf) then add nameserver addresses in Edit Connections | connection | Edit... | IPv4 Settings | Additional DNS servers; if necessary, remove DHCP-acquired nameserver addresses by setting Method to Automatic (DHCP) addresses only. -- 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+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 1163147] Re: can't resolve lan hosts (regression)
Where did you get the uvt program? -- 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+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 1163147] Re: can't resolve lan hosts (regression)
The instructions say you should comment out dns=dnsmasq in order to disable the system dnsmasq. But commenting out that line (and restarting network-manager) will only disable the NetworkManager- controlled dnsmasq instance (which listens at 127.0.1.1 in Quantal and higher, at 127.0.0.1 in Precise). If you have the dnsmasq package installed then you have another system dnsmasq instance running which listens by default on all network interfaces. Make sure that the dnsmasq package is not installed if you don't want this dnsmasq instance to be running. -- 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+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 1163147] Re: can't resolve lan hosts (regression)
*** This bug is a duplicate of bug 1126488 *** https://bugs.launchpad.net/bugs/1126488 I guess this is the same as bug #1126488. ** This bug has been marked a duplicate of bug 1126488 libvirt instance of dnsmasq in raring fails to forward DNS requests -- 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/1163147 Title: can't resolve lan hosts (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1163147/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Earlier there was some dispute about what the RFCs say about multiple nameservers. I found the following RFC which does have something to say about these issues. http://www.zoneedit.com/doc/rfc/rfc2182.txt Here are a couple of passages... Request for Comments: 2182 Category: Best Current Practice Selection and Operation of Secondary DNS Servers Abstract The Domain Name System requires that multiple servers exist for every delegated domain (zone). This document discusses the selection of secondary servers for DNS zones. Both the physical and topological location of each server are material considerations when selecting secondary servers. The number of servers appropriate for a zone is also discussed, and some general secondary server maintenance issues considered. [...] With multiple servers, usually one server will be the primary server, and others will be secondary servers. Note that while some unusual configurations use multiple primary servers, that can result in data inconsistencies, and is not advisable. The distinction between primary and secondary servers is relevant only to the servers for the zone concerned, to the rest of the DNS there are simply multiple servers. All are treated equally at first instance, even by the parent server that delegates the zone. Resolvers often measure the performance of the various servers, choose the best, for some definition of best, and prefer that one for most queries. That is automatic, and not considered 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
The target milestone should be adjusted, I guess. -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Hi Simon. Before I forget to ask: can you please update dnsmasq(8) to include under --strict-order a description of what happens when nameserver addresses are passed in via D-Bus instead of via a file? You wrote, you can very easily provide the same behaviour - only pass the first nameserver to dnsmasq Because NM doesn't use dnsmasq to cache, if NM were to give dnsmasq only one address then I guess the only service that dnsmasq would still provide is that of name-to-server mapping. And it turns out that the way NM currently uses dnsmasq to do this is seriously flawed. So I conclude that it's better for NM not to use dnsmasq at all until these problems are solved. [That NM only supplies one nameserver address per domain name] is a different problem, and could be solved. From the man page it's not completely clear how to solve it. Can you confirm (1) that it's possible to give multiple server options as follows server=/google.com/1.2.3.4 server=/google.com/5.6.7.8 and that the result will be that 1.2.3.4 and 5.6.7.8 will be treated equally for the purpose of resolving names in domain google.com? (2) And likewise via D-Bus? (3) What effect does strict-order have on this? Ironically, I think the problem arises because for nameservers associated with particular domains, the equivalent of --strict-order is always in play. What you say here suggests that my proposition #1 above is false. If #1 is false then it seems that in order to fix -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
[...cont'd after in order to fix...] bug #1072899, dnsmasq will have to be enhanced such that proposition #1 is true. But we can discuss the details of that in bug #1072899. parenthesis There is a close analogy between the problem here (bug #1003842) and a problem we have with avahi. Avahi resolves names in the domain .local. Networks should not use this TLD, but many do and at least in the past Microsoft actually recommended doing so. When users connect to such networks with avahi enabled the result is malfunction. Upstream purisitically says[*] If you come across a network where .local is a unicast DNS domain, please contact the local administrator and ask him to move his DNS zone to a different domain. If this is not possible, we recommend not to use Avahi in such a network at all. In practice avahi attempts to detect bad networks and disables itself if it thinks it is on a bad network, subject unfortunately both to false positives (bug #327362) and false negatives (bug #80900). We aren't yet doing even that well. We say that networks ought to have equivalent nameservers and we make no attempt to detect networks that have non-equivalent nameservers, of which there are very many. [*]http://avahi.org/wiki/AvahiAndUnicastDotLocal /parenthesis -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Simon wrote: Consider [...] server=/google.com/3.3.3.3 server=/google.com/4.4.4.4 [...] Queries sent to *google.com will be sent 3.3.3.3 or 4.4.4.4 in the same way as if strict order was set, ie, to 3.3.3.3 first, and only to 4.4.4.4 if 3.3.3.3 returns a SERVFAIL or REFUSED error, or doesn't reply at all. This should be changed, but the code which implements it is knarly and old, and won't stand more tinkering, it needs rewriting. I've not found the time, as of yet. That doesn't sound as if it's urgently needed for anything we are talking about here. What we do need is for strict-order to work when addresses are provided over D-Bus. (That this requires work: see #49. That this is needed: see below.) We say that networks ought to have equivalent nameservers and we make no attempt to detect networks that have non-equivalent nameservers, of which there are very many. Detect non-equivalent servers is hard. I'm very much in favour of doing it, if a way can be found. Well, let's look at the ideas that have been put forward so far. Solution #1. Disable NM-dnsmasq by default. This is the only solution we have right now. Other ideas that probably need more thought... Solution #2. Enhance dnsmasq such that it can be given an ordered list of nameservers via D-Bus and can process this list in strict-order fashion. Then do every lookup in strict-order fashion, but detect offline nameservers and omit them temporarily from the list. (This is my interpretation of Stéphane's suggestion in #37.) Solution #3. Enhance dnsmasq such that it can be given an ordered list of nameservers via D-Bus and can process this list in strict-order fashion. Then do a given lookup in strict-order fashion if * the lookup is being routed to a specific nameserver due to a server option; * the name is in one of the search domains returned by DHCP (as suggested my M T-L in #34); * the name is not in any of the recognized TLDs; or * we have detected nameserver nonequivalence since the last time the list of nameservers changed. The detection mechanism is as described in #28: on encountering NODATA or NXDOMAIN, dnsmasq returns the negative result immediately but also reiterates the query to all nameservers listed earlier than the one that answered. If one of those nameservers later returns an address then nameserver nonequivalence has been detected. (This combines several earlier suggestions.) -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Simon in #49: It doesn't work [...] the order of servers given to the DBus interface isn't preserved internally Aha, so the answer to my question Will switching on strict-order have the same effect now that nameserver addresses are sent over D-Bus? (in comment #42) is No. So switching strict-order back on is no solution. And solutions depending on strict-order including mine in #28 also won't work. Unless dnsmasq is somehow changed such that it remembers the order in which nameserver addresses come in over D-Bus so that strict-order is useful in the D-Bus case, if we want to avoid breaking name service on machines connected to NNNs then we have to disable dnsmasq by default; or disable it initially and only enable it when we know that we aren't on a NNN. (NNN = nonequivalent-nameserver network. As discussed in comment #5, such networks are not properly configured. But as observed several times, there are many NNNs out there. Which is why *many* people have been commenting out dns=dnsmasq.) There is another problem with NM-dnsmasq (bug #1072899). Some VPNs have multiple nameservers. NM uses dnsmasq to direct VPN domain name queries to the *first* one. But then, if the first one goes down, the second one is not tried. Once again, for the sake of speed enhancement in the favorable case, users suffer radical name service failure in the unfavorable case. This is not a good deal, IMHO. NM-dnsmasq should be disabled by default until these problems are solved. -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
there's still the unresolved question of whether re-enabling --strict-order will suffice as a workaround, since 12.10 relies on DBus to populate the nameservers. Is there any extra information on this? Please try it and report back. :-) (Put strict-order in a file in /etc/NetworkManager/dnsmasq.d/; stop network-manager; make sure all dnsmasq processes are dead; start network-manager.) -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1101002] Re: Frequently stops working for 15-30 seconds at a time on Ubuntu 12.10
Robie is right. In the failure case the resolver is contacting 127.0.1.1, where the NetworkManager-controlled dnsmasq process listens, rather than 127.0.0.1, where BIND named is listening. Robie is right, too, in saying that the instructions you followed have to be reinterpreted for Ubuntu. In Ubuntu /etc/resolv.conf is a symbolic link to the file /run/resolvconf/resolv.conf which is dynamically generated by the resolvconf utility. You can't edit /etc/resolv.conf directly; instead you have to configure the software that sends nameserver information to resolvconf. If you are running BIND named locally to provide general name service then you should almost certainly disable the NetworkManager-controlled dnsmasq process and use the local BIND instead. To disable the NetworkManager-controlled dnsmasq process, comment out the line dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf, then sudo stop network-manager sudo killall dnsmasq sudo start network-manager Next, configure BIND named to register its listen address with resolvconf. Edit /etc/default/bind9 and change RESOLVCONF=no to RESOLVCONF=yes, then do sudo service bind9 restart -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1101002 Title: Frequently stops working for 15-30 seconds at a time on Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+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 1042275] Re: dnsmasq should not register 127.0.0.1 with resolvconf if it's not listening on lo
** Description changed: - The system dnsmasq is preventing nameservice from working with - NetworkManager. By setting /etc/deafault/dnsmasq ENABLED=1 to ENABLED=0, - nameservice started working again. + The standalone Dnsmasq (from the dnsmasq package) is preventing the + NetworkManager-controlled dnsmasq from starting. By setting ENABLED=0 in + /etc/default/dnsmasq instead of ENABLED=1, name service started working + again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2 Uname: Linux 3.5.0-12-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Mon Aug 27 10:48:06 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: - TERM=xterm - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2012-08-27T10:43:43.717591 mtime.conffile..etc.dnsmasq.conf: 2012-05-26T23:51:39.391123 -- 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/1042275 Title: dnsmasq should not register 127.0.0.1 with resolvconf if it's not listening on lo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1042275/+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 1098152] Re: DNS resolve failed after upgrade from 12.04 to 12.10
*** This bug is a duplicate of bug 933723 *** https://bugs.launchpad.net/bugs/933723 ** This bug has been marked a duplicate of bug 933723 bind9 registers itself with resolvconf even though it's unable to provide name service -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1098152 Title: DNS resolve failed after upgrade from 12.04 to 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1098152/+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 969916] Re: host crashed with SIGSEGV in start_thread() on login
Compare bug #113417. ** Summary changed: - host crashed with SIGSEGV in start_thread() + host crashed with SIGSEGV in start_thread() on login ** Summary changed: - host crashed with SIGSEGV in start_thread() on login + host -t soa local. SIGSEGV in start_thread() on login -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/969916 Title: host -t soa local. SIGSEGV in start_thread() on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/969916/+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 113417] Re: [apport] host -t soa local crashed after resume from suspend
** Summary changed: - [apport] host crashed with SIGSEGV + [apport] host -t soa local crashed after resume from suspend ** Summary changed: - [apport] host -t soa local crashed after resume from suspend + [apport] host -t soa local SIGSEGV after resume from suspend -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/113417 Title: [apport] host -t soa local SIGSEGV after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/113417/+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 1103357] Re: Please backport dnsmasq 2.6.1 or later to Precise
** Summary changed: - dnsmasq 2.6.1 package update required for precise + Please backport dnsmasq 2.6.1 or later to Precise -- 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/1103357 Title: Please backport dnsmasq 2.6.1 or later to Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1103357/+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 1103357] Re: Please backport dnsmasq 2.6.1 or later to Precise
*** This bug is a duplicate of bug 1006898 *** https://bugs.launchpad.net/bugs/1006898 ** Description changed: Ubuntu Precise currently ships with dnsmasq 2.59, but due to the issue - reported in https://lists.launchpad.net/openstack/msg11696.html we - require that to be updated in Precise to at least 2.61. I see that - Quantal already has 2.63. Please backport this update for Precise! + reported in https://lists.launchpad.net/openstack/msg11696.html we need + at least 2.61. I see that Quantal already has 2.63. Please backport + dnsmasq 2.61 or later to Precise! ** This bug has been marked a duplicate of bug 1006898 [SRU] dnsmasq fails at leasing issues when using vlan mode -- 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/1103357 Title: Please backport dnsmasq 2.6.1 or later to Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1103357/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
@tombert: Probably not the same issue, since the issue being discussed here is not fixed by restarting. Please file a new bug report against dnsmasq with a detailed description of your problem. -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1098152] Re: DNS resolve failed after upgrade from 12.04 to 12.10
Not a NM problem; probably a dupe of #933723. ** Package changed: network-manager (Ubuntu) = bind9 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1098152 Title: DNS resolve failed after upgrade from 12.04 to 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1098152/+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 1045616] Re: DHCP server handing out DNS server addresses but DHCP client does not write these to resolv.conf
David, I suggest you get a Linux expert to help you at your location. ** Changed in: bind9 (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1045616 Title: DHCP server handing out DNS server addresses but DHCP client does not write these to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1045616/+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 1045616] Re: DHCP server handing out DNS server addresses but DHCP client does not write these to resolv.conf
David T wrote in comment #8: - Loaded Ubuntu 12.04 - Tried to install [a package] - couldn't resolve dns Possibly this is just another instance of bug #1000244. David T, can you reproduce the failure? ** Description changed: ARGH! Every release causes new problems :( If you have: linux DHCP server on the network with options: option domain-name xyz.com; option domain-name-servers 4.2.2.2, 4.2.2.3; - In Ubuntu 10.x it works fine and pulls the DHCP client pulls the DNS - servers from the DHCP fine. + In Ubuntu 10.x it works fine and the DHCP client pulls the DNS servers + from the DHCP fine. Ubuntu 12.x - It's broken. - Trying to fix with: adding to /etc/network/interfaces - dns-nameservers 4.2.2.2 4.2.2.3 - dns-search xyz.com - FAIL. Because you have iface eth0 inet dhcp that option isn't read - Try and configure with Network Manager from commandline because your running a server. - NOPE, network manager doesn't run from CLI commandline only GUI + Trying to fix with: adding to /etc/network/interfaces + + dns-nameservers 4.2.2.2 4.2.2.3 + dns-search xyz.com + + FAIL. Because you have + + iface eth0 inet dhcp + + that option isn't read + + Try and configure with NetworkManager from command line because you're + running a server. NOPE, NetworkManager doesn't run from CLI command + line, only GUI. Can't manually specify the DNS server in /etc/resolv.conf because it's always getting overwritten. What's the best option here? I think this might be a bug. Only option I haven't tried is using the head file from this description: - Resolvconf has a /etc/resolvconf/resolv.conf.d/ directory that can contain “base”, “head”, “original” and “tail” files. All in resolv.conf format. + Resolvconf has a /etc/resolvconf/resolv.conf.d/ directory that can + contain “base”, “head”, “original” and “tail” files. All in resolv.conf + format. + base: Used when no other data can be found - head: Used for the header of resolv.conf, can be used to ensure a DNS server is always the first one in the list - original: Just a backup of your resolv.conf at the time of resolvconf installation - tail: Any entry in tail is appended at the end of the resulting resolv.conf. In some cases, upgrading from a previous Ubuntu release, will make tail a symlink to original (when we think you manually modified resolv.conf in the past) + + head: Used for the header of resolv.conf, can be used to ensure a DNS server is + always the first one in the list + + original: Just a backup of your resolv.conf at the time of resolvconf + installation + + tail: Any entry in tail is appended at the end of the resulting + resolv.conf. In some cases, upgrading from a previous Ubuntu release, + will make tail a symlink to original (when we think you manually + modified resolv.conf in the past) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1045616 Title: DHCP server handing out DNS server addresses but DHCP client does not write these to resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1045616/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Stéphane? -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1091602] Re: Please enhance bind9 to use forwarder addresses from resolvconf
To anyone else who wants this feature: You are cordially invited to add your voice here. :-) Please explain how you intend to use the feature. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1091602 Title: Please enhance bind9 to use forwarder addresses from resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1091602/+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 1091602] Re: Please enhance bind9 to use forwarder addresses from resolvconf
** Bug watch added: Debian Bug tracker #687507 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687507 ** Also affects: resolvconf (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687507 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1091602 Title: Please enhance bind9 to use forwarder addresses from resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1091602/+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 1091602] Re: Please add resolvconf hook script to generate dynamic forwarders list
** No longer affects: bind ** Also affects: bind9 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483098 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1091602 Title: Please add resolvconf hook script to generate dynamic forwarders list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1091602/+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 933723] Re: bind9 registering itself with resolvconf but not set up to forward queries
Link to similar upstream bug report with title Please default to RESOLVCONF=no (Upstream bug report #483098 is now being tracked in Launchpad by wishlist bug #1091602 with title Please add resolvconf hook script to generate dynamic forwarders list.) ** Bug watch added: Debian Bug tracker #538674 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538674 ** Changed in: bind9 (Debian) Status: New = Unknown ** Changed in: bind9 (Debian) Remote watch: Debian Bug tracker #483098 = Debian Bug tracker #538674 ** Summary changed: - bind9 registering itself with resolvconf but not set up to forward queries + bind9 registers itself with resolvconf even though it's unable to provide name service -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/933723 Title: bind9 registers itself with resolvconf even though it's unable to provide name service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/933723/+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 1091602] Re: Please add resolvconf hook script to generate dynamic forwarders list
** Description changed:
- This is a wish. It is requested that the bind9 package include a
- resolvconf hook script /etc/resolvconf/update.d/bind9 which writes a
- forwarders{} statement to /var/run/named/forwarders based on the
- nameserver information in resolvconf's database. Then in order to use
- named in whole or in part as a forwarding nameserver the administrator
- can simply modify named.conf so that the latter includes
- /var/run/named/forwarders at the right place in the file. If this
- inclusion could be controlled by a setting in, e.g., /etc/default/bind9,
- then that would be even nicer.
+ It is requested that the bind9 package be enhanced such that named uses
+ forwarder addresses obtained from resolvconf's database.
- The file /etc/resolvconf/update.d/bind included in resolvconf versions
- 1.52 and earlier illustrates how such a hook script should be written.
- The latter file was written for BIND 8 and worked well; but due to
- limitations in BIND 8 it had to generate a whole options statement
- instead of just the forwarders part, which was less nice.
+ Such a feature would normally be implemented by means of a resolvconf
+ update hook script, in this case /etc/resolvconf/update.d/bind9. (It
+ must *not* be called /etc/resolvconf/update.d/bind since that was the
+ name of a script written for BIND 8 and included in earlier versions of
+ resolvconf.) Resolvconf update hook scripts get run every time the
+ database changes.
- I am prepared to write the needed script for BIND 9 and attach it here.
+ There are various ways to implement this proposal.
+
+ 1. Write out a forwarders{} statement
+
+ The script writes out a forwarders{} statement in the format of
+ named.conf(5) to /var/run/named/named.conf.forwarders and then does
+ /etc/init.d/bind9 reload to cause named to re-read its configuration
+ files.
+
+ To activate this, the admin has to edit /etc/bind/named.conf.options
+ such that it includes /var/run/named/named.conf.forwarders at the right
+ place.
+
+ The script /etc/resolvconf/update.d/bind that was included in resolvconf
+ versions 1.52 and earlier illustrates how such a hook script should be
+ written. The latter script was written for BIND 8 and worked well, but
+ due to limitations in BIND 8 it had to generate a whole options{}
+ statement instead of just the forwarders{} part.
+
+ 2. Write a list of forwarder addresses and enhance named to read this
+
+ The script writes out a simple list of IP addresses to
+ /var/run/named/forwarders and then triggers named to re-read its
+ forwarders list from this file. When run with a new option,
+ --forwarders-list=/var/run/named/forwarders, named uses the list in
+ /var/run/named/forwarders as its list of forwarder addresses instead of
+ whatever list was specified in the configuration file.
+
+ This approach requires that the option in question be added to named but
+ it has a number of advantages over the first approach. (1) It allows the
+ script to be much simpler. (2) It avoids run-time generation of
+ configuration files. (3) It avoids triggering the re-reading of
+ configuration files. (4) It allows the use of the resolvconf-based
+ forwarders list to be enabled and disabled via a variable in
+ /etc/default/bind9. (5) Some machines are still using an old script
+ written for bind8 which works as in #1 except that it writes out a whole
+ options{} statement instead of just a forwarders{} statement; the
+ present approach upgrades such machines cleanly.
--- BACKGROUND INFORMATION ---
As of Ubuntu 12.04, nameserver information is handled by resolvconf in
both the Server and Desktop editions of Ubuntu. Resolvconf maintains a
database of nameserver information, filed by interface name and
configuration agent. This is the information that is needed if named is
to be used in whole or in part as a forwarding nameserver.
BIND 9.7.x manual section 1.4.5.1: __Forwarding__. Even a caching name
server does not necessarily perform the complete recursive lookup
itself. Instead, it can forward some or all of the queries that it
cannot satisfy from its cache to another caching name server, commonly
referred to as a forwarder. There may be one or more forwarders, and
they are queried in turn until the list is exhausted or an answer is
found. Forwarders are typically used when you do not wish all the
servers at a given site to interact directly with the rest of the
Internet servers. A typical scenario would involve a number of internal
DNS servers and an Internet firewall. Servers unable to pass packets
through the firewall would forward to the server that can do it, and
that server would query the Internet DNS servers on the internal
server’s behalf.
-
- Currently it's possible to configure named to use a static list of
- forwarders, but to make use of a dynamic list a resolvconf hook script
- is needed.
--
You received this bug notification because you are a member of Ubuntu
[Bug 1091602] Re: Please add resolvconf hook script to generate dynamic forwarders list
** Description changed:
It is requested that the bind9 package be enhanced such that named uses
forwarder addresses obtained from resolvconf's database.
Such a feature would normally be implemented by means of a resolvconf
update hook script, in this case /etc/resolvconf/update.d/bind9. (It
must *not* be called /etc/resolvconf/update.d/bind since that was the
name of a script written for BIND 8 and included in earlier versions of
resolvconf.) Resolvconf update hook scripts get run every time the
database changes.
There are various ways to implement this proposal.
1. Write out a forwarders{} statement
The script writes out a forwarders{} statement in the format of
named.conf(5) to /var/run/named/named.conf.forwarders and then does
/etc/init.d/bind9 reload to cause named to re-read its configuration
files.
To activate this, the admin has to edit /etc/bind/named.conf.options
such that it includes /var/run/named/named.conf.forwarders at the right
place.
The script /etc/resolvconf/update.d/bind that was included in resolvconf
versions 1.52 and earlier illustrates how such a hook script should be
written. The latter script was written for BIND 8 and worked well, but
due to limitations in BIND 8 it had to generate a whole options{}
statement instead of just the forwarders{} part.
2. Write a list of forwarder addresses and enhance named to read this
The script writes out a simple list of IP addresses to
- /var/run/named/forwarders and then triggers named to re-read its
- forwarders list from this file. When run with a new option,
- --forwarders-list=/var/run/named/forwarders, named uses the list in
- /var/run/named/forwarders as its list of forwarder addresses instead of
- whatever list was specified in the configuration file.
+ /var/run/named/forwarders and then does /etc/init.d/bind9 reload to
+ cause named to re-read its configuration files. When run with a new
+ command-line option, --forwarders-list=/var/run/named/forwarders,
+ named uses the list in /var/run/named/forwarders as its list of
+ forwarder addresses instead of whatever was specified in options{}.
- This approach requires that the option in question be added to named but
- it has a number of advantages over the first approach. (1) It allows the
- script to be much simpler. (2) It avoids run-time generation of
- configuration files. (3) It avoids triggering the re-reading of
- configuration files. (4) It allows the use of the resolvconf-based
- forwarders list to be enabled and disabled via a variable in
- /etc/default/bind9. (5) Some machines are still using an old script
- written for bind8 which works as in #1 except that it writes out a whole
- options{} statement instead of just a forwarders{} statement; the
- present approach upgrades such machines cleanly.
+ This approach requires that the command-line option in question be added
+ to named but it has a number of advantages over the first approach. (1)
+ It allows the script to be much simpler. (2) It allows the use of the
+ resolvconf-based forwarders list to be enabled and disabled via a
+ variable in, e.g., /etc/default/bind9. (3) Some machines are still using
+ an old script written for bind8 which works as in #1 except that it
+ writes out a whole options{} statement instead of just a forwarders{}
+ statement; the present approach upgrades such machines cleanly.
+
+ 3. Enhance rndc to send, and named to receive, forwarder addresses
+
+ This has the advantages of approach #2 and also eliminates the need to
+ write out a file. The disadvantage is that it would be a significant
+ amount of extra work to extend the syntax of rndc.
--- BACKGROUND INFORMATION ---
As of Ubuntu 12.04, nameserver information is handled by resolvconf in
both the Server and Desktop editions of Ubuntu. Resolvconf maintains a
database of nameserver information, filed by interface name and
configuration agent. This is the information that is needed if named is
to be used in whole or in part as a forwarding nameserver.
BIND 9.7.x manual section 1.4.5.1: __Forwarding__. Even a caching name
server does not necessarily perform the complete recursive lookup
itself. Instead, it can forward some or all of the queries that it
cannot satisfy from its cache to another caching name server, commonly
referred to as a forwarder. There may be one or more forwarders, and
they are queried in turn until the list is exhausted or an answer is
found. Forwarders are typically used when you do not wish all the
servers at a given site to interact directly with the rest of the
Internet servers. A typical scenario would involve a number of internal
DNS servers and an Internet firewall. Servers unable to pass packets
through the firewall would forward to the server that can do it, and
that server would query the Internet DNS servers on the internal
server’s behalf.
** Summary changed:
- Please add resolvconf hook
[Bug 604283] Re: ntpd does not listen on 127.0.1.1, the IP address associated with the system hostname
Yes, I'd say that wontfix is appropriate unless someone comes forward with a reason why ntpd *should* listen at 127.0.1.1. P.S. I earlier wrote the following. It appears that bind9 operates in the same way. I added a virtual interface eth0:0 with a bogus address and named started listening on that without being restarted. I later discovered that this occurs because bind9 has a hook script in /etc/network/if-up.d/ which does rndc reconfig. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/604283 Title: ntpd does not listen on 127.0.1.1, the IP address associated with the system hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/604283/+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 1091602] [NEW] Please add resolvconf hook script to generate dynamic forwarders list
Public bug reported:
This is a wish. It is requested that the bind9 package include a
resolvconf hook script /etc/resolvconf/update.d/bind9 which writes a
forwarders{} statement to /var/run/named/forwarders based on the
nameserver information in resolvconf's database. Then in order to use
named in whole or in part as a forwarding nameserver the administrator
can simply modify named.conf so that the latter includes
/var/run/named/forwarders at the right place in the file. If this
inclusion could be controlled by a setting in, e.g., /etc/default/bind9,
then that would be even nicer.
The file /etc/resolvconf/update.d/bind included in resolvconf versions
1.52 and earlier illustrates how such a hook script should be written.
The latter file was written for BIND 8 and worked well; but due to
limitations in BIND 8 it had to generate a whole options statement
instead of just the forwarders part, which was less nice.
I am prepared to write the needed script for BIND 9 and attach it here.
--- BACKGROUND INFORMATION ---
As of Ubuntu 12.04, nameserver information is handled by resolvconf in
both the Server and Desktop editions of Ubuntu. Resolvconf maintains a
database of nameserver information, filed by interface name and
configuration agent. This is the information that is needed if named is
to be used in whole or in part as a forwarding nameserver.
BIND 9.7.x manual section 1.4.5.1: __Forwarding__. Even a caching name
server does not necessarily perform the complete recursive lookup
itself. Instead, it can forward some or all of the queries that it
cannot satisfy from its cache to another caching name server, commonly
referred to as a forwarder. There may be one or more forwarders, and
they are queried in turn until the list is exhausted or an answer is
found. Forwarders are typically used when you do not wish all the
servers at a given site to interact directly with the rest of the
Internet servers. A typical scenario would involve a number of internal
DNS servers and an Internet firewall. Servers unable to pass packets
through the firewall would forward to the server that can do it, and
that server would query the Internet DNS servers on the internal
server’s behalf.
Currently it's possible to configure named to use a static list of
forwarders, but to make use of a dynamic list a resolvconf hook script
is needed.
** Affects: bind
Importance: Unknown
Status: Unknown
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #483098
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483098
** Also affects: bind via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483098
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1091602
Title:
Please add resolvconf hook script to generate dynamic forwarders list
To manage notifications about this bug go to:
https://bugs.launchpad.net/bind/+bug/1091602/+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 604283] Re: Certain services do not listen on 127.0.1.1
For the reason explained in comment #17, setting to Invalid for bind9. ** Changed in: bind9 (Ubuntu) Status: Incomplete = Invalid ** Changed in: ntp (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/604283 Title: ntpd does not listen on 127.0.1.1, the IP address associated with the system hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/604283/+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 604283] Re: Certain services do not listen on 127.0.1.1
@Brian Burch: What is your opinion now about this report, insofar as it affects ntp? ** Summary changed: - Certain services do not listen on 127.0.1.1 + ntpd does not listen on 127.0.1.1, the IP address associated with the system hostname -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/604283 Title: ntpd does not listen on 127.0.1.1, the IP address associated with the system hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/604283/+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
