Re: default named.conf in bind ports and slaving from f-root

2017-04-17 Thread Olafur Gudmundsson
Hi Thomas, RFC7706 appendix B.1 is relevant here, https://tools.ietf.org/html/rfc7706#appendix-B.1 it strongly recommends relying on more than one provider just to avoid cases like this Strongly recommend that you add the all the other root servers (including F) to your patch along with

Re: default named.conf in bind ports and slaving from f-root

2017-04-16 Thread George Mitchell
On 04/16/17 05:30, Thomas Steen Rasmussen wrote: > On 04/16/2017 04:02 AM, George Mitchell wrote: >> On 04/14/17 08:37, Thomas Steen Rasmussen wrote: >>> Hello, >>> >>> Cloudflare deployed a bunch (74 apparently) of new f-root dns >>> servers, which do not permit AXFR like the other f-root

Re: default named.conf in bind ports and slaving from f-root

2017-04-16 Thread Thomas Steen Rasmussen
On 04/16/2017 04:02 AM, George Mitchell wrote: On 04/14/17 08:37, Thomas Steen Rasmussen wrote: Hello, Cloudflare deployed a bunch (74 apparently) of new f-root dns servers, which do not permit AXFR like the other f-root instances do. [...] A good alternative could be to change named.conf to

Re: default named.conf in bind ports and slaving from f-root

2017-04-15 Thread Kevin Oberman
On Sat, Apr 15, 2017 at 7:02 PM, George Mitchell wrote: > On 04/14/17 08:37, Thomas Steen Rasmussen wrote: > > Hello, > > > > Cloudflare deployed a bunch (74 apparently) of new f-root dns > > servers, which do not permit AXFR like the other f-root instances > > do. > >

Re: default named.conf in bind ports and slaving from f-root

2017-04-15 Thread George Mitchell
On 04/14/17 08:37, Thomas Steen Rasmussen wrote: > Hello, > > Cloudflare deployed a bunch (74 apparently) of new f-root dns > servers, which do not permit AXFR like the other f-root instances > do. > [...] > A good alternative could be to change named.conf to use > lax.xfr.dns.icann.org and

Re: default named.conf in bind ports and slaving from f-root

2017-04-15 Thread Bob Willcox
On Fri, Apr 14, 2017 at 05:25:21PM +0200, Thomas Steen Rasmussen wrote: > On 04/14/2017 04:51 PM, Mathieu Arnold wrote: > > Hi, > > > > I'm busy right now, could you open a PR so that I don't loose and forget > > this ? > > Sure thing, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218656 > >

Re: default named.conf in bind ports and slaving from f-root

2017-04-14 Thread Thomas Steen Rasmussen
On 04/14/2017 04:51 PM, Mathieu Arnold wrote: Hi, I'm busy right now, could you open a PR so that I don't loose and forget this ? Sure thing, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218656 /Thomas ___ freebsd-ports@freebsd.org mailing

Re: default named.conf in bind ports and slaving from f-root

2017-04-14 Thread Mathieu Arnold
Hi, I'm busy right now, could you open a PR so that I don't loose and forget this ? Le 14/04/2017 à 14:37, Thomas Steen Rasmussen a écrit : > Hello, > > Cloudflare deployed a bunch (74 apparently) of new f-root dns > servers, which do not permit AXFR like the other f-root instances > do. > >

default named.conf in bind ports and slaving from f-root

2017-04-14 Thread Thomas Steen Rasmussen
Hello, Cloudflare deployed a bunch (74 apparently) of new f-root dns servers, which do not permit AXFR like the other f-root instances do. Since our bind ports default configs suggest slaving . and arpa from f-root this is a big problem in the cases where anycast routing makes your requests hit