On Tue, May 20, 2014 at 4:22 PM, Stephane Bortzmeyer wrote:
> The problem is indeed in
> 172.in-addr.arpa (botched rollover, it seems, old KSK 30729 removed
> from the zone while the DS was - is - still in many caches).
>
Not only in caches, but while it was still being served from the
in-addr.ar
On Tue, May 20, 2014 at 04:14:27PM -0400,
Jared Mauch wrote
a message of 20 lines which said:
> > http://dnsviz.net/d/16.172.in-addr.arpa
>
> Is this perhaps related to AS112 project as well or 172.16 zones
> being built-in to some resolvers?
The OP made a small typo in the URL. The problem
On May 20, 2014, at 7:13 AM, cgielen+dnso...@gielen.name wrote:
> DNSSEC-validation fails for 172.in-addr.arpa . This causes reverse DNS
> lookups to fail for all IPv4-address starting with 172.
>
> http://dnsviz.net/d/16.172.in-addr.arpa
Is this perhaps related to AS112 project as well or 172.
DNSSEC-validation fails for 172.in-addr.arpa . This causes reverse DNS
lookups to fail for all IPv4-address starting with 172.
http://dnsviz.net/d/16.172.in-addr.arpa
--
Casper Gielen | LIS UNIX
PGP fingerprint = 16BD 2C9F 8156 C242 F981 63B8 2214 083C F80E 4AF7
Universiteit van Tilburg | Post
