string)
>TCP source address (null-terminated string)
>Rdata type (null-terminated string)
>Key (null-terminated string)
>TKEY token length (4 bytes, network byte order)
>TKEY token (remainder of packet)
> The daemon replies with a four-byte value in network byte orde
I think the normal way to do this is run a syslog server on the host
running bind, which is configured to just forward all log messages to
the remote syslog server. Otherwise, bind would have to implement the
syslog network protocol(s) itself, rather than just use the system
standard local syslog f
Disclaimer: I'm new to trying gss-tsig as an update method, so it is
entirely possible I'm doing something completely stupid.
I'm using bind 9.7.3 (because it ships with RedHat 6), with an Active
Directory as the kerberos infrastructure.
If I use the following update-policy:
grant * subdomain my
3 matches
Mail list logo
