Bind db.root outdated, backport only the db.root file, for LTS important to keep db.root updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Fix Released
|
Medium
|
LaMont Jones |
Bug Description
In Precise the Bind9 db.root file is outdated. We need to keep this file updated especially as Precise gets older over time. As time passes this file will become more and more out of date. It may be possible to backport just the single file and that would make an SRU easier.
Please consider updating the db.root file only and leaving the rest of Bind9 alone.
Current file dated January 3, 2013: http://
Current Precise date: June 17, 2010
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bind9 1:9.8.1.
ProcVersionSign
Uname: Linux 3.5.0-26-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Tue Mar 26 10:09:29 2013
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214)
MarkForUpload: True
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageV
bind9utils 1:9.8.1.
apparmor 2.7.102-0ubuntu3.7
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
Also see bug 1090593.
That addresses the issue of an old published root server IP that will stop responding in the future, causing a small (few second) delay in the one thirteenth of startups where bind will time out before it is able to bootstrap the latest root NS records from one of the other root servers.
LaMont wanted to go further and backport the entire root zone file as you suggested. I remain unconvinced that there is any point, since I don't see how there will be any impact on the hints file being behind in general since it picks up the latest records from any root server it can find on startup. But LaMont is the Debian maintainer for bind and the conclusion was to go with the full backport.
Subscribing and assigning LaMont, since AIUI he's already going to do this for bug 1090593. But I'll keep the bugs separate for now, since bug 1090593 is that D is out of date, this bug is that they're all out of date, and it is possible to resolve one bug without the other.