BIND9 and AS112

Diarmuid O Briain diarmuid at obriain.com
Fri Mar 9 12:28:18 UTC 2018


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
associated with that service ?

(2)
I guess therefore that I have the server working and that these are the
only errors. The basic unicast tests on my AS112 server (199.9.9.204/
2a99:9:9::204) are working:

ubuntu at lxd1:~$ *dig @199.9.9.204 <http://199.9.9.204/> -x 192.168.10.1*
Returns a QUERY, status: *NXDOMAIN*

ubuntu at lxd1:~$ *dig -6 @2a99:9:9::204 netlabsug.tst. AAAA*
Returns a QUERY, status: *REFUSED*

However quite frankly I do not get how the AS112 service is accessed via
anycast. So if I do a reverse-lookup to the IXP DNS server (199.9.9.201/
2a99:9:9::201) that is for a private IP address.

ubuntu at lxd1:~$ *dig @199.9.9.201 <http://199.9.9.201/> -x 192.168.10.1*
Returns a QUERY, status: *NXDOMAIN*

I also get an NXDOMAIN response. When I monitor that on the IXP DNS server I
see:

*09-Mar-2018 08:47:43.710 client 199.9.9.100#48061
(1.10.168.192.in-addr.arpa): query: 1.10.168.192.in-addr.arpa IN PTR +E
(199.9.9.201)*

If I disable the AS112 service

ubuntu at as112:~$ *sudo systemctl stop bind9.service*

and perform the same test to the IXP DNS.

*09-Mar-2018 08:49:39.230 client 199.9.9.100#43253
(1.10.168.192.in-addr.arpa): query: 1.10.168.192.in-addr.arpa IN PTR +E
(199.9.9.201)*

I am not sure how this decision is actually made by BIND. I have
logging set to *debug* and enabled most logging categories but no more
information is popping into the log to enlighten me.

(3)
Another thing that is confusing me is the fact that the* named.conf *file
in RFC7534 has no IPv6 zones directed to *db.db-empty*.

Any ideas ?

thanks for your help.

regards,

Diarmuid





--

*Irish by birth, located in Uganda but Munster by the grace of God.*



On 9 March 2018 at 15:01, Ray Bellis <ray at isc.org> wrote:

> 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:
> > Mar 09 08:11:43 as112 named[3787]: internal_send: 2620:4f:8000::42#53:
> > Invalid argument
>
> Do you have functioning IPv6 connectivity?
>
> The errors suggest that you don't, but that your named.conf is expecting
> that you do.
>
> Ray
>
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20180309/01b75367/attachment.html>


More information about the bind-users mailing list