Re: BIND9 and AS112

2018-10-22 Thread Havard Eidnes
Hi, reviving an old thread with some new information: > 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

Re: BIND9 and AS112

2018-03-09 Thread Stephane Bortzmeyer
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

Re: BIND9 and AS112

2018-03-09 Thread Stephane Bortzmeyer
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

Re: BIND9 and AS112

2018-03-09 Thread Diarmuid O Briain
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

Re: BIND9 and AS112

2018-03-09 Thread Ray Bellis
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: >

BIND9 and AS112

2018-03-09 Thread Diarmuid O Briain
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: