Hi,
I am not sure this is intended behavior, or maybe I should file a bug.
I am doing some tests with dnstap and bind (9.18.6 now but I see the same
behavior with older 9.18 versions). I am using
dnstap-go.
I have configured bind to use dnstap with no other options and using a Unix
domain socket. (On named.conf, dnstap {all;};).
If I start named but the dnstap collector is not running it will never try to
connect. I need to start the dnstap program
_before_ starting named.
>From the named.conf documentation I assumed that bind would retry the dnstap
>connection periodically. (fstrm-reopen-interval).
Is that correct or I am making a wrong assumption? I think at least it would be
desirable to have bind reconnect in case the dnstap
collector was restarted for whatever reason.
Versions:
bind 9.18.6
fstrm-0.6.1
protobuf-3.20.1,1
protobuf-c-1.4.0_3
Thanks!
Borja.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
