Hai, > > 3.Patching "named.conf" template to load the correct bind9 module (i.e 9.11) > I _think_ samba_dnsupgradedns writes a new config fragment. No you need adjustments in bind as shown below. after the 4 points, im missing the following. Addding point 5. The end result should look like this: ls -al /var/lib/samba/bind-dns/
total 28 drwxrwx--- 3 root bind 4096 Apr 24 08:17 . drwxr-xr-x 10 root root 4096 Apr 8 15:03 .. drwxrwx--- 3 root bind 4096 Feb 27 16:38 dns -rw-r----- 2 root bind 877 Apr 28 2015 dns.keytab -rw-r--r-- 1 root root 781 Feb 27 16:38 named.conf -r--r--r-- 1 root root 312 Feb 27 16:41 named.conf.update -rw-r--r-- 1 root root 2092 Feb 27 16:38 named.txt Take note that dns.keytab isnt moved by default but should be moved. This is one i did manualy. After that change you need to adjust : /etc/bind/named.conf.options. // https://wiki.samba.org/index.php/Dns-backend_bind // DNS dynamic updates via Kerberos (optional, but recommended) // old path //tkey-gssapi-keytab "/var/lib/samba/private/dns.keytab"; tkey-gssapi-keytab "/var/lib/samba/bind-dns/dns.keytab"; and in : /etc/bind/named.conf.local. change // adding the dlopen ( Bind DLZ ) module for samba, include "/var/lib/samba/bind-dns/named.conf"; Now bind9 restart then samba restart. to make sure the restart order is correct and it always works. systemctl edit samba-ad-dc.service # /etc/systemd/system/samba-ad-dc.service.d/override.conf [Unit] After=network.target network-online.target bind9.service Maybe its an option to add it as default that samba always starts after bind9 started. Greetz, Louis
