#dnstap — Public Fediverse posts

This tool, DNS-collector, seems interesting.
Do some #dns people have feedback about it?
Or perhaps alternative/additional tools to try?

I suppose #dnstap (or @PowerDNS streams) is the most efficient way to collect data.

From: @dmachard
https://fosstodon.org/@dmachard/113672780996845324

@jelu - grand, thanks for the clarification. Given the fact that #unbound and #nlnetlabs tend to deliver solid quality, I believe it must be my gut feeling or the #DNSTAP collector.

By any chance, can you recommend some collector to for file-based archiving? I am using the GoLang-dnstap, but I would rather have a service that periodically logrotates the output files.

Question to the #DNS operators out there:

I am sure, you've heard of #dnstap. Can someone briefly elaborate on the pros and cons of unix sockets vs. TCP sockets? My (experimental) setup uses dnstap over TCP to log to a central service, but first experiments just feel slightly unreliable. Would local logging on a Unix socket and uploading the log files via #cron solve this? Or is it just my gut feeling, but dnstap over TCP sockets is just as reliable?

I am using #unbound if that helps.

Thanks for any helpful response.

Messing about with dns I have learned of #dnstap. Pretty brilliant way to handle streaming logs. All without impacting IOs from regular stdout.😍 Oh and vector.dev has forwarding support. 😎

https://dnstap.info/

NLnetLabs released update 1.16.0 for #Unbound, so I released a fresh build of my Unbound #docker image! I've enabled the #DNSTAP feature as requested. 🤗

Enjoy!

https://hub.docker.com/r/madnuttah/unbound
https://github.com/madnuttah/unbound-docker

#opensource #dns