Re: CNAME at apex, was Re: Issue running "dig txt rs.dns-oarc.net" on 9.12

On Fri, Mar 09, 2018 at 03:23:33PM +, Tony Finch wrote: > Alternatively, maybe the patch below is OK? (Based on Nick @ NNEX's > observation.) My idea is that if we have been chasing a CNAME (so are at > risk of deadlock) but we are looking for a DS (so we will query the > parent) we can go ahea

Re: Suggestions for a distributed DNS zone hosting solution I'm designing

Hi, > Am 09.03.2018 um 15:26 schrieb Timothe Litt : > >> On 08-Mar-18 07:52, Tony Finch wrote: >> Best way to achieve this is with anycast, which can be pretty >> time-consuming to set up - try searching for Nat Morris's presentation >> "anycast on a shoestring" which he gave at several NOG meet

CNAME at apex, was Re: Issue running "dig txt rs.dns-oarc.net" on 9.12

Cathy Almond wrote: > > [snip] > > validating rs.dns-oarc.net/CNAME: checking existence of DS at > 'rs.dns-oarc.net' > validating rs.dns-oarc.net/CNAME: continuing validation would lead to > deadlock: aborting validation > validating rs.dns-oarc.net/CNAME: deadlock found (create_fetch) > > The r

Re: Re: Suggestions for a distributed DNS zone hosting solution I'm designing

On 08-Mar-18 07:52, Tony Finch wrote: > Best way to achieve this is with anycast, which can be pretty > time-consuming to set up - try searching for Nat Morris's presentation > "anycast on a shoestring" which he gave at several NOG meetings. > The advantage of anycast (as opposed to having NS recor

Re: BIND9 and AS112

On Fri, Mar 09, 2018 at 03:28:18PM +0300, Diarmuid O Briain wrote a message of 427 lines which said: > However quite frankly I do not get how the AS112 service is accessed via > anycast. Did you configure your routing as mentioned in section 3.4 of RFC 7534? > Another thing that is confusing

Re: Suggestions for a distributed DNS zone hosting solution I'm designing

Latitude wrote: I must deploy a DNS system with the following requirements: - single master server, multiple slave servers - minimal time for name resolving for Americas, Europe and Asia On 08.03.18 12:52, Tony Finch wrote: Best way to achieve this is with anycast, which can be pretty time-co

Re: BIND9 and AS112

On Fri, Mar 09, 2018 at 12:32:41PM +0300, Diarmuid O Briain wrote a message of 122 lines which said: > Mar 09 08:11:43 as112 named[3787]: internal_send: 2620:4f:8000::42#53: > Invalid argument > Mar 09 08:11:43 as112 named[3787]: internal_send: 192.175.48.42#53: Invalid > argument I suspect t

Re: BIND9 and AS112

Ray, (1) Ah that makes sense. When you say functioning I am presuming you mean to the public Internet and not just in my testbed ? I have IPv6 configured on the testbed nameserver too but I guess only for internal testbed IP addresses. The AS112 server much be checking the anycast addresses associ

Re: BIND9 and AS112

On 09/03/2018 05:32, Diarmuid O Briain wrote: > Hi, > > I have been following RFC7534 to setup an AS112 Service. I am getting > the following errors from /*systemctl*/ status, what do they mean ? > > Mar 09 08:11:43 as112 named[3787]: > ../../../../lib/isc/unix/socket.c:2104: unexpected error: >

Re: Suggestions for a distributed DNS zone hosting solution I'm designing

On Thu, Mar 08, 2018 at 12:52:57PM +, Tony Finch wrote a message of 49 lines which said: > Best way to achieve this is with anycast, which can be pretty > time-consuming to set up - try searching for Nat Morris's > presentation "anycast on a shoestring" which he gave at several NOG > meeti

BIND9 and AS112

Hi, I have been following RFC7534 to setup an AS112 Service. I am getting the following errors from *systemctl* status, what do they mean ? Mar 09 08:11:43 as112 named[3787]: ../../../../lib/isc/unix/socket.c:2104: unexpected error: Mar 09 08:11:43 as112 named[3787]: internal_send: 2620:4f:8000::