On Mon, Feb 13, 2017 at 8:03 AM, Tony Finch <d...@dotat.at> wrote: > There are several ways to avoid this pitfall: > > Use TCP > > Look for an NSEC(3) record > > Query for the specific types you want to know about
The pitfall comes from unexamined muscle-memory assumptions when inspecting a DNS response, so none of those methods avoid it. They're expecting people to remember that longstanding behavior has changed without providing any clue about it.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
