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:
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.
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.=
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