I am encountering the exact same problem as described in this bug report.
A patch seems available and should fix the problem.
When reloading bind while I have samba setup as a PDC and using BIND9_DLZ module, the zone is deleted.
Restarting named makes it work again but is not usable since many scripts (logrotate) use reload by default.
Issuing a simple "rndc zonestatus ad.zone" just after restart is OK, and after reload I get a "rndc: 'zonestatus' failed: not found
no matching zone 'ad.zone' in any view"
This may cause a lot of trouble for dynamic updates on somewhat complex setups with Samba as a PDC (samba internal DNS server is really limited...)
I have reported the bug on Ubuntu first ( https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1670450 ), you may find more information there but the patch in univention bugtracker seems to correct the problem even on latest samba versions (4.6.x)
Sorry to bump this bug report but I don't think it has been fixed in 4.7.0. Any news ?
Bug still present as of Samba 4.7.x (on Ubuntu 18.04 LTS)
We have been unable to reproduce this issue. If it still happens on current Samba and current BIND9 we would very much like detailed debug information and steps to reproduce.
Hai Andres, i tried that also to see if it still exist, it looks solved.
But i cant verify it, since all my servers are on latest versions atm.
If the problem exist in older versions on Debian/Ubuntu, the workaround ( with systemd ) is:
systemctl edit bind9.service
( results in file : /etc/systemd/system/bind9.service.d/override.conf )
And i suggest change samba-ad-dc.service also a bit so it loads after bind9
systemctl edit samba-ad-dc.service
After=network.target network-online.target bind9.service
(results in file: /etc/systemd/system/samba-ad-dc.service.d/override.conf )
systemctl restart bind9 samba-ad-dc
And you never see this problem again.