Fwd: About dnstap feature

[Champion Xie]

After executing rndc dnstap -reopen, the properties of the dnstap-output
object file changed, and the original named became root. Of course, I used
the root user to execute the rndc command. At this time, executing
dnstap-read again will report an error, and the query log cannot be written
to the dnstap-output object file. In addition, after executing rndc dnstap
-reopen, you must execute rndc reconfig again to use dnstap-read to query
the record.

error info
[image: image.png]


In addition, does ISC have any plans to continuously optimize the dnstap
function? I think the dnstap function is very good and we need it. Of
course, there is still a long way to go. We need to improve the development
of dnstap related functions, as well as the best practices of dnstap and
the improvement of related manuals.


-- 
Best Regards!!
champion_xie


-- 
Best Regards!!
champion_xie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20240919/bb7b57d8/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 26014 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20240919/bb7b57d8/attachment-0001.png>