In particular the generalized notifications (RFC 9859) specifies in 4.2.1 that eg. a NOTIFY(CDS) that includes an EDNS(0) ER option and where an update (of the parent-side DS) would break stuff may trigger an outbound Error Reporting Query like
_er.59.example.com.6._er.errors.ns1.example.net. TXT
to be sent.
We need:
In particular the generalized notifications (RFC 9859) specifies in 4.2.1 that eg. a NOTIFY(CDS) that includes an EDNS(0) ER option and where an update (of the parent-side DS) would break stuff may trigger an outbound Error Reporting Query like
_er.59.example.com.6._er.errors.ns1.example.net. TXT
to be sent.
We need:
Support in (most likely the tdns-agent) for acting as a reporting agent for RFC 9567 DNS Error Reports. I.e. when it gets queries to [stuff].agent.comain. then the [stuff] should be parsed apart to create a reasonable error report on a log somewhere.
Support in dog for attaching an EDNS(0) ER option to queries.
Support in tdns-server for detecting the EDNS(0) ER option and passing that along with the query so that a subsequent error report query may be generated if needed and desired.