Hey @wcawijngaards @vvfedorenko, I see support was added for kernel timestamping of client queries in #882. Looks like it's conditionally enabled only if the new sock_queue_timeout option is enabled?

Any chance the kernel timestamp could be enabled and used (if available) instead of re-fetching the timestamp in the dnstap code?

The dnstap code is going to run some time after the client query packet hits the machine, potentially after many context switches, etc., so the accuracy of the dnstap timestamp can certainly suffer if the query is being re-timestamped after getting the packet from the kernel.

Thanks!