It appears that Matteo Contrini  <[email protected]> said:
>- According to Section 5.1 of RFC 9824 a resolver can also request an 
>authoritative server to respond with NXDOMAIN even when compact NSEC is 
>used, with the CO flag. At the moment, Cloudflare and NS1 authoritative 
>servers don't appear to support this, while Bunny DNS does. For this to 
>be useful, however, the CO flag needs to be set by both the resolver and 
>the query client (otherwise the NXDOMAIN would be reverted to NOERROR). 
>DNS libraries don't set this bit by default (nor does "dig"), so an 
>implementation needs to be aware that they should set also the CO flag 
>when they use the DO flag.

As I said, the intention was for resolvers to recover NXDOMAIN. If
they don't do that, I'd say it's a bug, and I'd rather fix the
resolvers to maintain the behavior they've had for the past 40 years
than try to add workrounds in every application in the world that uses
the DNS.

>Did I get this right? If so, I still think that RFC 9989 is at least 
>missing some guidance for developers:

If we are going down that road, you need to file an erratum for every
RFC that mentions NXDOMAIN.  But please don't.

R's,
John

_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to