Re: BIND9 TSIG from Windows Server 2016 DNS Server Zone

2022-05-27 Thread Bob Harold
On Fri, May 27, 2022 at 3:29 PM Mirsad Goran Todorovac < mirsad.todoro...@alu.unizg.hr> wrote: > Hi Crist, > > 1. Actually, I am running dynamic updates with BIND9 and ISC DHCP server > for about a half a year and I am frankly very happy with the way it works. > This is at the Academy. So, I am

Re: BIND9 TSIG from Windows Server 2016 DNS Server Zone

2022-05-27 Thread Mirsad Goran Todorovac
Hi Crist, 1. Actually, I am running dynamic updates with BIND9 and ISC DHCP server for about a half a year and I am frankly very happy with the way it works. This is at the Academy. So, I am familiar with the dynamic (DDNS) updates. Though there had been some tricky stuff with sub-/24 reverse

Re: BIND9 TSIG from Windows Server 2016 DNS Server Zone

2022-05-26 Thread Crist Clark
As far as I know, GSS-TSIG is only used for DNS updates, not zone transfers. https://bind9.readthedocs.io/en/v9_16_5/advanced.html#dynamic-update Sorry, don't know what capabilities AD has for securing zone transfers beyond IP ACLs, which of course is not much security at all. I've never had

BIND9 TSIG from Windows Server 2016 DNS Server Zone

2022-05-25 Thread Mirsad Goran Todorovac
Dear all, I have a zone local.grf.hr administered by AD, DHCP and DDNS ran by Windows Server 2016 (not by my architectural choice). However, since Windows Server 2016 had round-robin strategy of inquiring the forwarders, it performed worse than BIND9 on old Debian server. So, I had the

BIND9 TSIG from Windows Server 2016 DNS Server Zone

2022-05-25 Thread Mirsad Goran Todorovac
Dear all, I have a zone local.grf.hr administered by AD, DHCP and DDNS ran by Windows Server 2016 (not by my architectural choice). However, since Windows Server 2016 had round-robin strategy of inquiring the forwarders, it performed worse than BIND9 on old Debian server. So, I had the

BIND9 TSIG from Windows Server 2016 DNS Server Zone

2022-05-25 Thread Mirsad Goran Todorovac
Dear all, I have a zone local.grf.hr administered by AD, DHCP and DDNS ran by Windows Server 2016 (not by my architectural choice). However, since Windows Server 2016 had round-robin strategy of inquiring the forwarders, it performed worse than BIND9 on old Debian server. So, I had the