From a95dc83de543e0a5637f50c9b2e3facadbcb1f3c Mon Sep 17 00:00:00 2001
From: Tinderbox User server_id_string
; ]
[ directory path_name
; ]
[ dnstap { message_type
; ... } ; ]
- [ dnstap-output ( file
| unix
) path_name
; ]
+ [ dnstap-output ( file
| unix
) path_name
[ size size_spec
] [ versions ( number
| unlimited
) ] ; ]
[ dnstap-identity ( string
| hostname
| none
) ; ]
[ dnstap-version ( string
| none
) ; ]
[ fstrm-set-buffer-hint number
; ]
@@ -3010,6 +3010,19 @@ badresp:1,adberr:0,findfail:0,valfail:0]
(provided with libfstrm) is listening on
the socket.)
+ If the first argument is file
, then
+ two additional options can be added:
+ size indicates the size to which a
+ dnstap log file can grow before being
+ rolled to a new file, and versions
+ specifies the number of rolled log files to retain. These
+ are similar to the size and
+ versions options in a
+ logging channel. The default
+ is to allow dnstap log files to grow to
+ any size without rolling.
+
dnstap-output can only be set globally in options. Currently, it can only be diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html index ebec1569e0..2af0c377cd 100644 --- a/doc/arm/Bv9ARM.ch09.html +++ b/doc/arm/Bv9ARM.ch09.html @@ -176,6 +176,26 @@
+ Query logic has been substantially refactored (e.g. query_find + function has been split into smaller functions) for improved + readability, maintainability and testability. [RT #43929] +
+
+ dnstap logfiles can now be configured to
+ automatically roll when they reach a specified size. If
+ dnstap-output is configured with mode
+ file
, then it can take optional
+ size and versions
+ key-value arguments to set the logfile rolling parameters.
+ (These have the same semantics as the corresponding
+ options in a logging channel statement.)
+ [RT #44502]
+
dig +ednsopt now accepts the names @@ -220,7 +240,7 @@ always have the name ".", which can be ambiguous.)
- In the event you need to manipulate a a zone actually + In the event you need to manipulate a zone actually called "-redirect", use a trailing dot: "-redirect."
@@ -260,12 +280,6 @@ was sent. [RT #43595]
- The built in mangaged keys for the global root zone have been - updated to include the upcoming key signing key (keyid 20326). -
-Expanded and improved the YAML output from @@ -299,15 +313,15 @@
- Named could deadlock there were multiple changes to - NSEC/NSEC3 parameters for a zone being processed at the - same time. [RT #42770] + named could deadlock if multiple changes + to NSEC/NSEC3 parameters for the same zone were being processed + at the same time. [RT #42770]
- Named could trigger a assertion when sending notify - messages. [RT #44019] + named could trigger an assertion when + sending NOTIFY messages. [RT #44019]
+ Query logic has been substantially refactored (e.g. query_find + function has been split into smaller functions) for improved + readability, maintainability and testability. [RT #43929] +
+
+ dnstap logfiles can now be configured to
+ automatically roll when they reach a specified size. If
+ dnstap-output is configured with mode
+ file
, then it can take optional
+ size and versions
+ key-value arguments to set the logfile rolling parameters.
+ (These have the same semantics as the corresponding
+ options in a logging channel statement.)
+ [RT #44502]
+
dig +ednsopt now accepts the names @@ -183,7 +203,7 @@ always have the name ".", which can be ambiguous.)
- In the event you need to manipulate a a zone actually + In the event you need to manipulate a zone actually called "-redirect", use a trailing dot: "-redirect."
@@ -223,12 +243,6 @@ was sent. [RT #43595]
- The built in mangaged keys for the global root zone have been - updated to include the upcoming key signing key (keyid 20326). -
-Expanded and improved the YAML output from @@ -262,15 +276,15 @@
- Named could deadlock there were multiple changes to - NSEC/NSEC3 parameters for a zone being processed at the - same time. [RT #42770] + named could deadlock if multiple changes + to NSEC/NSEC3 parameters for the same zone were being processed + at the same time. [RT #42770]
- Named could trigger a assertion when sending notify - messages. [RT #44019] + named could trigger an assertion when + sending NOTIFY messages. [RT #44019]