[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
@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
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
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
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
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
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
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
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
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
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
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
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
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
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
** 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
** 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
--
** 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
** 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
--
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.
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.
[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.
[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
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'
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'
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.
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
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
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
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
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.
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
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
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
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
35 matches
Mail list logo
