Precise reached EOL some time ago. Marking this "won't fix"
** Changed in: bind9 (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593
Title:
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: bind9 (Ubuntu Lucid)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: bind9 (Ubuntu Lucid)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: bind9 (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: bind9 (Ubuntu Quantal)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: bind9 (Ubuntu Oneiric)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
oneiric has seen the end of its life and is no longer receiving any
updates. Marking the oneiric task for this ticket as Won't Fix.
** Changed in: bind9 (Ubuntu Oneiric)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As noted in http://d.root-servers.org/renumber.html, the change will be
done on the 3rd Jan and the old IP address will be retried 6 months
later.
Could we get proposed-update packages before the 3rd Jun (when the old
IP will stop responding)?
I'm presuming that the Ubuntu guys are waiting until
As noted in http://d.root-servers.org/renumber.html, the change will be
done on the 3rd Jan and the old IP address will be retried 6 months
later.
Could we get proposed-update packages before the 3rd Jun (when the old
IP will stop responding)?
I'm presuming that the Ubuntu guys are waiting until
** Changed in: bind9 (Ubuntu Quantal)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu Precise)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu Oneiric)
Assignee: (unassigned) = LaMont Jones (lamont)
--
You received this bug
** Changed in: bind9 (Ubuntu Quantal)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu Precise)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu Oneiric)
Assignee: (unassigned) = LaMont Jones (lamont)
--
You received this bug
I wasn't happy to ask for sponsorship for SRUs directly from LaMont's
changes, since they included some autotools noise and updated the entire
db.root file instead of just changing the IP of D.ROOT-SERVERS.NET. For
example, they added new IPv6 entries in older releases that weren't
there before.
** Patch added: hardy.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508775/+files/hardy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: lucid.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508776/+files/lucid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: oneiric.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508777/+files/oneiric.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508778/+files/precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Patch added: quantal.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508779/+files/quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
I wasn't happy to ask for sponsorship for SRUs directly from LaMont's
changes, since they included some autotools noise and updated the entire
db.root file instead of just changing the IP of D.ROOT-SERVERS.NET. For
example, they added new IPv6 entries in older releases that weren't
there before.
** Patch added: hardy.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508775/+files/hardy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593
Title:
** Patch added: lucid.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508776/+files/lucid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593
Title:
** Patch added: oneiric.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508777/+files/oneiric.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593
** Patch added: precise.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508778/+files/precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593
** Patch added: quantal.debdiff
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+attachment/3508779/+files/quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593
Confirmed fixed in raring on 1:9.9.2.dfsg.P1-2.
** Changed in: bind9 (Ubuntu Raring)
Status: Triaged = Fix Released
--
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/1090593
** Description changed:
+ [Impact]
+
+ named may use the wrong server for D.ROOT-SERVERS.NET on startup, as the
+ IP address is changing. This will cause a startup delay as it times out
+ and bootstraps from another root server instead. In the worst case, a
+ malicious actor on the old IP could
Confirmed fixed in raring on 1:9.9.2.dfsg.P1-2.
** Changed in: bind9 (Ubuntu Raring)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593
Title:
** Description changed:
+ [Impact]
+
+ named may use the wrong server for D.ROOT-SERVERS.NET on startup, as the
+ IP address is changing. This will cause a startup delay as it times out
+ and bootstraps from another root server instead. In the worst case, a
+ malicious actor on the old IP could
An SRU into existing releases makes good sense. The change is very
minimal, with the biggest risk being that somepoint after the current
operator of D stops using the IP address, said address gets assigned to
someone who decides that giving out the wrong answers would be a thing
to do. I don't
I've uploaded SRU-able versions of the package to my personal ppa. See
https://launchpad.net/~lamont/+archive/ppa/+packages
--
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/1090593
An SRU into existing releases makes good sense. The change is very
minimal, with the biggest risk being that somepoint after the current
operator of D stops using the IP address, said address gets assigned to
someone who decides that giving out the wrong answers would be a thing
to do. I don't
I've uploaded SRU-able versions of the package to my personal ppa. See
https://launchpad.net/~lamont/+archive/ppa/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1090593
Title:
If it's not a trivial change or has potential for unexpected problems
then, fair enough i agree. Just leave it out until at least bind pushes
out a new version with the updated zone file. I suppose a 1/13 chance of
a minor delay on the first query to a server after reboot isn't much to
worry
Although not a serious problem, admins running LTS releases could be waiting a
long time for the packages to include the correct IPv4 D root server.
I asked LaMont Jones, one of the Debian bind9 maintainers, about this D root
change issue and he said:
It's fixed in 1:9.8.4.dfsg.P1-2, and will
This should be SRU'd to all supported releases. Its not a low
Importance. Slowing down peoples' lookups 1/13th of the time is pretty
lame. Also we do backport fixes like this when things outside Ubuntu
change, such as an address of a service. There's no maintenance problem
for merges, as its fixed
Note that as part of due diligence I checked this site for confirmation
that this is the legitimate IP of d:
https://www.iana.org/domains/root/servers
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
If it's not a trivial change or has potential for unexpected problems
then, fair enough i agree. Just leave it out until at least bind pushes
out a new version with the updated zone file. I suppose a 1/13 chance of
a minor delay on the first query to a server after reboot isn't much to
worry
Although not a serious problem, admins running LTS releases could be waiting a
long time for the packages to include the correct IPv4 D root server.
I asked LaMont Jones, one of the Debian bind9 maintainers, about this D root
change issue and he said:
It's fixed in 1:9.8.4.dfsg.P1-2, and will
This should be SRU'd to all supported releases. Its not a low
Importance. Slowing down peoples' lookups 1/13th of the time is pretty
lame. Also we do backport fixes like this when things outside Ubuntu
change, such as an address of a service. There's no maintenance problem
for merges, as its fixed
Note that as part of due diligence I checked this site for confirmation
that this is the legitimate IP of d:
https://www.iana.org/domains/root/servers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In response to Robie, As far as i'm aware, a recursive server will pick
a random root name server to fetch the list of root name servers from.
If this happens to be the D root server old ip is offline, it'll stall
briefly while trying to connect to it. Granted it's only a once off and
a 1/13
Considering it's such an easy patch, no reason not to apply it though.
For the development release, it adds extra work to whoever does merges
in the future, and introduces the risk of an accidental regression if
not everything through to upstream has updated before Ubuntu. But if you
get the
In response to Robie, As far as i'm aware, a recursive server will pick
a random root name server to fetch the list of root name servers from.
If this happens to be the D root server old ip is offline, it'll stall
briefly while trying to connect to it. Granted it's only a once off and
a 1/13
Considering it's such an easy patch, no reason not to apply it though.
For the development release, it adds extra work to whoever does merges
in the future, and introduces the risk of an accidental regression if
not everything through to upstream has updated before Ubuntu. But if you
get the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
In the past, I don't believe we've updated the hints file by introducing
a delta in Ubuntu, since it isn't expected to cause any operational
problems for just a single root server in the hints file to be out of
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
In the past, I don't believe we've updated the hints file by introducing
a delta in Ubuntu, since it isn't expected to cause any operational
problems for just a single root server in the hints file to be out of
45 matches
Mail list logo
