Collector to logging protobuf streams from PowerDNS servers. The DNS-collector has a full Protobuf Logging support for PowerDNS's products.
Settings:
-
listen-ip
(str)Set the local address that the server will bind to. If not provided, the server will bind to all available network interfaces (0.0.0.0).
-
listen-port
(int)Set the local port that the server will listen on. If not provided, use the default port.
-
tls-support
(bool)Enables or disables TLS (Transport Layer Security) support. If set to true, TLS will be used for secure communication.
-
tls-min-version
(str)Specifies the minimum TLS version that the server will support.
-
cert-file
(str)Specifies the path to the certificate file to be used for TLS. This is a required parameter if TLS support is enabled.
-
key-file
(str)Specifies the path to the key file corresponding to the certificate file. This is a required parameter if TLS support is enabled.
-
sock-rcvbuf
(int)This advanced parameter allows fine-tuning of network performance by adjusting the amount of data the socket can receive before signaling to the sender to slow down. Sets the socket receive buffer in bytes SO_RCVBUF. Set to zero to use the default system value.
-
reset-conn
(bool)Set whether to send a TCP Reset to force the cleanup of the connection on the remote side when the server exits.
-
chan-buffer-size
(int)Specifies the maximum number of packets that can be buffered before discard additional packets. Set to zero to use the default global value.
-
add-dns-payload
(bool)PowerDNS protobuf message does not contain a DNS payload; use this setting to add a raw DNS payload.
Defaults:
- name: powerdns
powerdns:
listen-ip: 0.0.0.0
listen-port: 6001
tls-support: false
tls-min-version: 1.2
cert-file: ""
key-file: ""
reset-conn: true
chan-buffer-size: 0
add-dns-payload: false
If you logs your DNS traffic in basic text format, you can use the specific directives:
powerdns-tags[:INDEX]
: get all tags separated by comma, or the tag according to the provided INDEXpowerdns-original-request-subnet
: get original request subnet like edns subclientpowerdns-applied-policy
: get applied policypowerdns-applied-policy-hit
: get applied policy hitpowerdns-applied-policy-kind
: get applied policy kindpowerdns-applied-policy-trigger
: get applied policy triggerpowerdns-applied-policy-type
: get applied policy typepowerdns-metadata[:KEY]
: get all metadata separated by comma or specific one if a valid KEY is providedpowerdns-http-version
: http version used with DoH queries
Configuration example:
- name: console
stdout:
mode: text
text-format: "timestamp-rfc3339ns identity qr qname qtype powerdns-metadata:selected_pool"
If you logs your DNS traffic in JSON output, the following part will be added in your DNS logging messages.
"powerdns": {
"tags": [],
"original-request-subnet": "",
"applied-policy": "rpzbasic",
"applied-policy-hit": "local-a.org",
"applied-policy-kind": "Custom",
"applied-policy-trigger": "local-a.org.",
"applied-policy-type": "QNAME",
"metadata": {
"agent":"Go-http-client/1.1",
"selected_pool":"pool_internet"
},
"http-version": "HTTP3"
}
Example to enable logging in your dnsdist
rl = newRemoteLogger("<dnscollectorip>:6001")
local metadata = { selected_pool='pool', agent='doh-header:user-agent' }
addAction(AllRule(),RemoteLogAction(rl, nil, {serverID="dnsdist"}, metadata))
addResponseAction(AllRule(),RemoteLogResponseAction(rl, nil, true, {serverID="dnsdist"}, metadata))
addCacheHitResponseAction(AllRule(), RemoteLogResponseAction(rl, nil, true, {serverID="dnsdist"}, metadata))
Example to enable logging in your pdns-recursor
/etc/pdns-recursor/recursor.conf
lua-config-file=/etc/pdns-recursor/recursor.lua
/etc/pdns-recursor/recursor.lua
protobufServer("<dnscollectorip>:6001", {exportTypes={pdns.A, pdns.AAAA, pdns.CNAME}})
outgoingProtobufServer("<dnscollectorip>:6001")
with RPZ
rpzFile("/etc/pdns-recursor/basic.rpz", {
policyName="custom",
tags={"tag"}
})