[Bug 1670450] Re: samba4 bind dlz module stops working on rndc reload

[Stéphane Berthelot]

Hello,

I've just installed bionic (18.04) beta2 with samba 4.7.6 and bind
9.11.3 and the problem is still present.

Is there any mean to get this bug fixed soon ? How do others avoid the
problem with dlz zone deleted on rndc reload ?

I reproduced the bug using the procedure on #5 (if needed)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1670450

Title:
  samba4 bind dlz module stops working on rndc reload

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Triaged

Bug description:
  I am encountering the exact same problem as described in this bug report.
  A patch seems available and should fix the problem.

  https://forge.univention.org/bugzilla/show_bug.cgi?id=39139

  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...)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Mar  6 19:00:47 2017
  InstallationDate: Installed on 2017-02-24 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8)
  NmbdLog:

  OtherFailedConnect: Yes
  SambaServerRegression: No
  SmbConfIncluded: Yes
  SmbLog:

  SourcePackage: samba
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1670450/+subscriptions