enabling TLS communication between primary and secondary

lso-notify { 214.7.78.109 port 853 tls tlsblockname; }; also how is it possible configure secondary to listen on port 853 over tls? because on secondary we can use tls block name with primaries block only and not with listen-on option. *Best Regards,* *Vikas Sharma* -- Visit https://lis

Re: Behavior of port tag in options clause is ambiguous

ify” servers to be notified on port 53. > Yup, it’s doing that. Those servers happen to be the secondaries too. > > Not sure exactly what you’re try to accomplish with these settings, > especially that “port” configuration, but it looks like it’s behaving > consistently with the doc

Re: Behavior of port tag in options clause is ambiguous

ut notification is going to port 53 as well. So when port 15010 will be used and when port 53 will be used while sending notification to secondary DNS? *BR,* *Vikas Sharma* On Fri, Dec 16, 2022 at 12:11 PM Ondřej Surý wrote: > Hi, > > there’s really nice documentation for BIND 9, and

Behavior of port tag in options clause is ambiguous

010; listen-on port 15010 { 127.0.0.1; }; also-notify { 10.1.2.4 port 53; 10.1.2.5 port 53; }; }; Best Regards, Vikas Sharma -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the developmen