cynicalsecurity :cm_2:<p>Ha, some <a href="https://bsd.network/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNSSEC</span></a> gotcha for you people out there, especially if you are in RIPE.</p><p>It looks like several ISPs within RIPE have started using DNSSEC also on their in-addr.arpa and ip6.arpa zones! So, when they delegate to you, if your zone is not signed… it doesn't work _if the originating resolver specified the DNSSEC flag_.</p><p>So, what does it look like? You query from a machine which does not automatically request DNSSEC and everything works fine (assuming the intermediate resolver does not use DNSSEC), you query using, say, 9.9.9.9 (Quad9) and it doesn't work (i.e. your PTR records don't resolve).</p><p>This is even more obvious if you are being delegated a sub-/24 zone using the CNAME trick as the NS specified in the delegating zone are not going to be signed and the recursion fails mysteriously.</p><p>Anyway, dig +trace is your friend as are these three wonderful sites:</p><p>* <a href="https://bind9.readthedocs.io/en/stable/dnssec-guide.html#easy-start-guide-for-signing-authoritative-zones" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bind9.readthedocs.io/en/stable</span><span class="invisible">/dnssec-guide.html#easy-start-guide-for-signing-authoritative-zones</span></a><br>* <a href="https://dnssec-debugger.verisignlabs.com" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dnssec-debugger.verisignlabs.c</span><span class="invisible">om</span></a><br>* <a href="https://dnsviz.net" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="">dnsviz.net</span><span class="invisible"></span></a></p><p>:flan_hacker:</p>