These particular options control which RR fields are recorded into the C-DNS data for a particular message after that message is captured. They do not filter the captured messages based on the RRTYPE of the first Question in the Query, which some users might expect because the current documentation is a little ambiguous.
The corresponding --accept-opcode options do result in messages that don't meet the filter being discarded- see https://datatracker.ietf.org/doc/html/rfc8618#section-6.2.2 to see the distinction in the C-DNS specification.
Updates are needed to both the User Guide and the sample compactor file to make this behaviour clearer.
These particular options control which RR fields are recorded into the C-DNS data for a particular message after that message is captured. They do not filter the captured messages based on the RRTYPE of the first Question in the Query, which some users might expect because the current documentation is a little ambiguous.
The corresponding --accept-opcode options do result in messages that don't meet the filter being discarded- see https://datatracker.ietf.org/doc/html/rfc8618#section-6.2.2 to see the distinction in the C-DNS specification.
Updates are needed to both the User Guide and the sample compactor file to make this behaviour clearer.