Bug 173077 - BIND slaves root and arpa zones on wrong servers
Summary: BIND slaves root and arpa zones on wrong servers
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 10.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-25 18:10 UTC by Damien Fleuriot
Modified: 2017-12-31 22:27 UTC (History)
0 users

See Also:


Attachments
file.diff (571 bytes, patch)
2012-10-25 18:10 UTC, Damien Fleuriot
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Damien Fleuriot 2012-10-25 18:10:00 UTC
From /etc/namedb/named.conf , when using the Slaving mechanism for the root and arpa zones, BIND slaves from F.ROOT-SERVERS.NET.

The commentary lines however recommend using ICANN's XFR servers at:
xfr.lax.dns.icann.org.
xfr.cjr.dns.icann.org.


Is using F an oversight ?

We've had problems at work when our /etc/namedb/slave/root.slave and arpa.slave zones expired after the F root server denied AXFRs from our IPs for over a week.

Moving to ICANN's XFR servers solves our problem.

Fix: Patch attached to use ICANN's XFR servers instead of F.ROOT-SERVERS.NET

Patch attached with submission follows:
Comment 1 Borja Marcos 2013-05-07 10:10:10 UTC
I wouldn't advise to use this unless  it's really closely monitored.

The zone statement in bind's configuration file needs IP addresses, not =
names, to specify master servers. So, if the IP addresses change the =
configuration can be useless.

Actually this happened on April 30th 2013.  The listed IP addresses are =
obsolete.

xfr.lax.dns.icann.org was 192.0.32.140, now it is 192.0.32.132
xfr.cjr.dns.icann.org was 192.0.47.140, now it is 192.0.47.132

I haven't seen any notice.
Comment 2 Damien Fleuriot 2013-05-07 20:06:24 UTC
On 7 May 2013, at 11:10, Borja Marcos <borjam@sarenet.es> wrote:

> I wouldn't advise to use this unless  it's really closely monitored.
>=20
> The zone statement in bind's configuration file needs IP addresses, not na=
mes, to specify master servers. So, if the IP addresses change the configura=
tion can be useless.
>=20
> Actually this happened on April 30th 2013.  The listed IP addresses are ob=
solete.
>=20
> xfr.lax.dns.icann.org was 192.0.32.140, now it is 192.0.32.132
> xfr.cjr.dns.icann.org was 192.0.47.140, now it is 192.0.47.132
>=20
> I haven't seen any notice.
>=20

Neither have I, and it caused us trouble just today when our caches expired.=
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:26 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped