Re: [Pdns-users] PowerDNS Authoritative 4.6.2, how to log served responses (i.e. NOERROR, NXDOMAIN, SERVFAIL, etc)?

2022-06-14 Thread Otto Moerbeek via Pdns-users
Hello, Network sniffing based logging is one option. Additionally, PowerDNS Recursor itzelf can log client queries and/or repsonses using protobufs. It also can log outgoing queries and/or their responses in dnstap format. Both methods can handle large query loads. See https://docs.powerdns.com

Re: [Pdns-users] PowerDNS Authoritative 4.6.2, how to log served responses (i.e. NOERROR, NXDOMAIN, SERVFAIL, etc)?

2022-06-14 Thread Klaus Darilion via Pdns-users
Hi Dmitriy! Recently we had a similar requirement for our resolvers (which only do query logging, not response logging) and we decided to use packetbeat for this purpose. IT should be easy to integrate if you have an existing Elasic Search cluster! regards Klaus Von: Pdns-users Im Auftrag vo

Re: [Pdns-users] PowerDNS Authoritative 4.6.2, how to log served responses (i.e. NOERROR, NXDOMAIN, SERVFAIL, etc)?

2022-06-14 Thread frank+pdns--- via Pdns-users
Hi Dmitriy, https://doc.powerdns.com/authoritative/settings.html#log-dns-queries states that it logs "all incoming DNS queries", not the results. If you want to log the results, you'll need to either increase the loglevel,

[Pdns-users] PowerDNS Authoritative 4.6.2, how to log served responses (i.e. NOERROR, NXDOMAIN, SERVFAIL, etc)?

2022-06-14 Thread Dmitriy Koff via Pdns-users
Hello! I'm trying to configure log for PowerDNS (4.6.2) and cannot figure how to log served responses (i.e. NOERROR, NXDOMAIN, SERVFAIL, etc) /etc/pdns/pdns.conf (parameters regarding logs) loglevel=5 log-dns-details=yes log-dns-queries=yes query-logging=no # nslookup example.com 127.0.0.1 Serve

[Pdns-users] dnsdist 1.7.2 released

2022-06-14 Thread Remi Gacogne via Pdns-users
Hello! We are very happy to release dnsdist 1.7.2 today, a maintenance release fixing a few bugs reported since 1.7.1: - An unhandled exception could happen when an invalid protocol was used in an incoming DNS over HTTPS forwarded-for header and passed to the backend via the proxy protocol,