Re: Administrivia.

2018-04-23 Thread Ray Bellis
On 23/04/2018 16:34, Chris Thompson wrote: > To further increase our Schadenfreude, please do let the list know just > how ISC managed to let that happen! Or will you be able to blame ARIN? We're blaming ARIN :p 149.20/16 was previously delegated to us with its own DNSKEY / DS, and then we used

Re: Administrivia.

2018-04-23 Thread Chris Thompson
On Apr 23 2018, Ray Bellis wrote: On 23/04/2018 14:18, Anand Buddhdev wrote: If you repeat your query with the +cd option, you'll get a response. DNSViz shows problems with the DNSSEC setup of this zone. The DS and DNSKEY records don't match: http://dnsviz.net/d/1.20.149.in-addr.arpa/dnssec/

Re: Administrivia.

2018-04-23 Thread Ray Bellis
On 23/04/2018 14:18, Anand Buddhdev wrote: > If you repeat your query with the +cd option, you'll get a response. > > DNSViz shows problems with the DNSSEC setup of this zone. The DS and > DNSKEY records don't match: > > http://dnsviz.net/d/1.20.149.in-addr.arpa/dnssec/ Thanks for the heads up

Re: Administrivia.

2018-04-23 Thread Anand Buddhdev
On 23/04/2018 15:02, G.W. Haywood via bind-users wrote: > Below is from our own DNS server; I get the same response from all the > public servers that I've tried. > > 8<-- > mail6:~$ >>> dig -x 149.20.1.60 > > ; <<>> DiG 9.9.5-9

Administrivia.

2018-04-23 Thread G.W. Haywood via bind-users
Hi there, It looks like something has recently changed in the ISC DNS. 8<-- Apr 20 09:00:36 mail6 sm-mta[20203]: NOQUEUE: connect from lists.isc.org [149.20.1.60] Apr 20 13:00:22 mail6 sm-mta[29448]: NOQUEUE: connect from lists