John Todd

See Andrew Campling's Encrypted DNS weekly call from 2022-05-30 - Andrey Meshkov gave a presentation on AdGuard's experiences with DoQ. He mentions that they will be making their DoQ-specific components...

That's probably a good start. Making the two have uniform reporting characteristics would be useful, and if the number of attempted connections is difficult, then at least do what is...

+1 here. Being able to ingest recursor traffic is ideal for identifying trends on authoritative servers or performance on instances. We have a protobuf model for this, but DNSTAP would...

To update after reading rgacogne's comments: I think we need to have at least the option to support packetcache hits as output. DNSTAP is used for all sorts of statistics...

Agreed. However, doing sampled or intermittent dnstap collection with all packets captured is easier than building two parallel systems when debugging issues. Perhaps a flag that allows packetcache capture is...

DoQ and DoH/3 (https://github.com/PowerDNS/pdns/issues/8914) would be really welcome, but as usual, saying "I want a feature!" is not a way to get a feature. But also just looking to get...

Speaking for Quad9: support for HTTP/3 support in dnsdist is a pre-requisite for it to appear on Quad9 service addresses. That doesn't guarantee it will, but we're typically quite welcoming...

This is even more useful with the "TopN" model, just by itself. Given the flexibility of the pipeline and filter concepts, having separate prometheus instances would solve a significant number...

Perhaps having maximums of time for storing each type of data (qname, IP address) and a total maximum number of bytes allowed in a pool for each of those would...

Parse error summary file as described. [dnstap-parse-errors.gz](https://github.com/vectordotdev/vector/files/14231991/dnstap-parse-errors.gz)