[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bind9 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
@Simon thanks for testing this on Jammy. AIUI Jammy's bind9 behaves in the best possible way: - Doesn't spam the logs with errors if an address is missing; - Starts listening on the address as soon as it becomes available. This looks like a Fix Released to me, but I'd like confirmation from you and/or Vihai. I'm marking this as Incomplete for now. I don't think this is SRU material, but we can consider adding Triaged+Low tasks for the stable releases for tracking. ** Changed in: bind9 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
I tested on a Jammy machine running bind9 1:9.18.1-1ubuntu1 and there, bind9 won't complain if the IPv6 address it is supposed to listen on is missing. Bind9 will simply start listening when the IP finally shows up. This makes it more resilient to IPv6 DAD taking time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
I'm not sure if everyone is having the issue here. But if in named.conf you're explicitly binding to a particular address, then you need to *also* configure named to start only after that interface is configured. See https://lists.ubuntu.com/archives/ubuntu-devel/2021-May/041455.html for some fairly recent discussion on this. The exact nature of this has changed over the years since this bug was first opened; since systemd was introduced in 16.04, it's systemd that is relevant. Some users might find that adding After=network-online.target works for them. The ML thread goes more into why this isn't the default. ** Tags added: network-online-ordering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
This bug is still present in 20.04. It does not matter if I have listen-on-ipv6 set to a specific address or any. Still the described behaviour is seen. As a workaround if I set a static IPv6 address on the interface it works. But if the interface is set to auto, or there is a slight delay in setting the address otherwise the problem reappears. IMHO the solution is that network.target in should not pass until ipv6 auto address mechanism has had a chance to run. This will delay the boot by a second or two. But it will ensure that the interface has an address when daemons start to bind to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
I was having the same problem on a new dns server (Ubuntu 10.04 LTS) but not on an old one (Ubuntu 10.04LTS). I noticed that the two /etc/network/interface had a different order for iface lines and moving inet6 before ipv4 ipaliases solved the problem. ### WORKING ONE ### auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 93.x netmask 255.255.254.0 network 93.xx broadcast 93.xx iface eth0 inet6 static address 2a01: netmask 64 gateway 2a01: up ip -6 addr add 2a01:x/64 dev eth0 auto eth0:NS1 iface eth0:NS1 inet static address 93.xx netmask 255.255.254.0 # END ## ### BROKEN ONE ### auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 93.x netmask 255.255.254.0 network 93.xx broadcast 93.xx auto eth0:NS1 iface eth0:NS1 inet static address 93.xx netmask 255.255.254.0 iface eth0 inet6 static address 2a01: netmask 64 gateway 2a01: up ip -6 addr add 2a01:x/64 dev eth0 END # -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
I was having the same problem on a new dns server (Ubuntu 10.04 LTS) but not on an old one (Ubuntu 10.04LTS). I noticed that the two /etc/network/interface had a different order for iface lines and moving inet6 before ipv4 ipaliases solved the problem. ### WORKING ONE ### auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 93.x netmask 255.255.254.0 network 93.xx broadcast 93.xx iface eth0 inet6 static address 2a01: netmask 64 gateway 2a01: up ip -6 addr add 2a01:x/64 dev eth0 auto eth0:NS1 iface eth0:NS1 inet static address 93.xx netmask 255.255.254.0 # END ## ### BROKEN ONE ### auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 93.x netmask 255.255.254.0 network 93.xx broadcast 93.xx auto eth0:NS1 iface eth0:NS1 inet static address 93.xx netmask 255.255.254.0 iface eth0 inet6 static address 2a01: netmask 64 gateway 2a01: up ip -6 addr add 2a01:x/64 dev eth0 END # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
The problem is still present, and it is really annoying. I can't understand why it has been classified with a Low importance. -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
The problem is still present, and it is really annoying. I can't understand why it has been classified with a Low importance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Just upgraded to oneiric, bug persists sigh -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Just upgraded to oneiric, bug persists sigh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
bind9 starts at boot but before all interfaces are UP. It's because of parallel boot (upstart) -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
bind9 starts at boot but before all interfaces are UP. It's because of parallel boot (upstart) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
I have a near-identical issue. During boot, this gets logged: named[770]: could not get query source dispatcher (2001:::::xxx#0) named[770]: loading configuration: address not available named[770]: exiting (due to fatal error) Manually starting BIND fixes the issue. This is the named.conf line in question: query-source-v6 address 2001:::::xxx port *; I believe it's because the IPv6 address is marked 'tentative' while the IPv6 duplicate-address-detection process is in progress, and BIND is starting before it's finished. -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
I have a near-identical issue. During boot, this gets logged: named[770]: could not get query source dispatcher (2001:::::xxx#0) named[770]: loading configuration: address not available named[770]: exiting (due to fatal error) Manually starting BIND fixes the issue. This is the named.conf line in question: query-source-v6 address 2001:::::xxx port *; I believe it's because the IPv6 address is marked 'tentative' while the IPv6 duplicate-address-detection process is in progress, and BIND is starting before it's finished. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/510587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
** Changed in: bind9 (Ubuntu) Status: New = Triaged -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
** Changed in: bind9 (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
** Changed in: bind9 (Ubuntu) Status: Expired = New -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
** Changed in: bind9 (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
This problem is still very present on Maverick A notable fact might be that I explicitly bind to certain IPv6 addresses instead of the default all interfaces -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
This problem is still very present on Maverick A notable fact might be that I explicitly bind to certain IPv6 addresses instead of the default all interfaces -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bind9 (Ubuntu) Status: Incomplete = Expired -- 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/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
[Expired for bind9 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bind9 (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510587 Title: Bind/named does not initialize on boot due to missing IPv6 address -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
This bug is still present in lucid release, just upgraded 4 boxes and Bind didn't start at boot while it started when launched manually. May 3 13:10:08 sid named[893]: starting BIND 9.7.0-P1 -u bind May 3 13:10:08 sid named[893]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions' 'CPPFLAGS=' May 3 13:10:08 sid named[893]: adjusted limit on open files from 1024 to 1048576 May 3 13:10:08 sid named[893]: found 4 CPUs, using 4 worker threads May 3 13:10:08 sid named[893]: using up to 4096 sockets May 3 13:10:08 sid named[893]: loading configuration from '/etc/bind/named.conf' May 3 13:10:08 sid named[893]: reading built-in trusted keys from file '/etc/bind/bind.keys' May 3 13:10:08 sid named[893]: using default UDP/IPv4 port range: [1024, 65535] May 3 13:10:08 sid named[893]: using default UDP/IPv6 port range: [1024, 65535] May 3 13:10:08 sid named[893]: not listening on any interfaces May 3 13:10:08 sid named[893]: generating session key for dynamic DNS May 3 13:10:08 sid named[893]: could not get query source dispatcher (62.212.1.11#0) May 3 13:10:08 sid named[893]: loading configuration: address not available May 3 13:10:08 sid named[893]: exiting (due to fatal error) It may be triggered by the fact that I explicitly bind on specific network addresses, however is is still present. -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in ubuntu. -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
This bug is still present in lucid release, just upgraded 4 boxes and Bind didn't start at boot while it started when launched manually. May 3 13:10:08 sid named[893]: starting BIND 9.7.0-P1 -u bind May 3 13:10:08 sid named[893]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions' 'CPPFLAGS=' May 3 13:10:08 sid named[893]: adjusted limit on open files from 1024 to 1048576 May 3 13:10:08 sid named[893]: found 4 CPUs, using 4 worker threads May 3 13:10:08 sid named[893]: using up to 4096 sockets May 3 13:10:08 sid named[893]: loading configuration from '/etc/bind/named.conf' May 3 13:10:08 sid named[893]: reading built-in trusted keys from file '/etc/bind/bind.keys' May 3 13:10:08 sid named[893]: using default UDP/IPv4 port range: [1024, 65535] May 3 13:10:08 sid named[893]: using default UDP/IPv6 port range: [1024, 65535] May 3 13:10:08 sid named[893]: not listening on any interfaces May 3 13:10:08 sid named[893]: generating session key for dynamic DNS May 3 13:10:08 sid named[893]: could not get query source dispatcher (62.212.1.11#0) May 3 13:10:08 sid named[893]: loading configuration: address not available May 3 13:10:08 sid named[893]: exiting (due to fatal error) It may be triggered by the fact that I explicitly bind on specific network addresses, however is is still present. -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! When reporting bugs in the future please use apport, either via the appropriate application's Help - Report a Problem menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bind9 (Ubuntu) Importance: Undecided = Low ** Changed in: bind9 (Ubuntu) Status: New = Incomplete -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in ubuntu. -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
This is odd. You would expect the address to be available when you configured it. Can you include your network config in /etc/network/interfaces for this interface? -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in ubuntu. -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Mark, Attached you find a copy of /etc/network/interfaces. Chuck, 1. the specific steps or actions you took that caused you to encounter the problem, rebooted the box 2. the behavior you expected, and bind not failing 3. the behavior you actually encountered (in as much detail as possible). bind failed to listen Okay, irony apart, what other informations do you need? When reporting bugs in the future please use apport, either via the appropriate application's Help - Report a Problem menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Yup, thanks. ** Attachment added: interfaces http://launchpadlibrarian.net/38368235/interfaces -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in ubuntu. -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Hmm, the interfaces file looks ok. Funny thing is, if you didn't change anything between booting and starting bind, the interfaces are created to slow and the bug should be filed on something else than bind. It's the right thing to do for bind, if the interface isn't there. -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in ubuntu. -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Yes, it could well be an issue in upstart or in some related-script, unfortunately I'm not familiar with upstart, thus I'd have to spend some time to figure out where the problem is (and at the moment the time is lacking...). -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in ubuntu. -- 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 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! When reporting bugs in the future please use apport, either via the appropriate application's Help - Report a Problem menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: bind9 (Ubuntu) Importance: Undecided = Low ** Changed in: bind9 (Ubuntu) Status: New = Incomplete -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
This is odd. You would expect the address to be available when you configured it. Can you include your network config in /etc/network/interfaces for this interface? -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Mark, Attached you find a copy of /etc/network/interfaces. Chuck, 1. the specific steps or actions you took that caused you to encounter the problem, rebooted the box 2. the behavior you expected, and bind not failing 3. the behavior you actually encountered (in as much detail as possible). bind failed to listen Okay, irony apart, what other informations do you need? When reporting bugs in the future please use apport, either via the appropriate application's Help - Report a Problem menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Yup, thanks. ** Attachment added: interfaces http://launchpadlibrarian.net/38368235/interfaces -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Hmm, the interfaces file looks ok. Funny thing is, if you didn't change anything between booting and starting bind, the interfaces are created to slow and the bug should be filed on something else than bind. It's the right thing to do for bind, if the interface isn't there. -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address
Yes, it could well be an issue in upstart or in some related-script, unfortunately I'm not familiar with upstart, thus I'd have to spend some time to figure out where the problem is (and at the moment the time is lacking...). -- Bind/named does not initialize on boot due to missing IPv6 address https://bugs.launchpad.net/bugs/510587 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
