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)
--
Reported upstream (univention is 3rd party)
** Bug watch added: Samba Bugzilla #12931
https://bugzilla.samba.org/show_bug.cgi?id=12931
** Changed in: samba
Remote watch: forge.univention.org/bugzilla/ #39139 => Samba Bugzilla #12931
--
You received this bug notification because you are a
Hm I looked at current samba git and bugtracker and did not find anything
related to this bug. It seems noone ever submitted this upstream...
This is quite strange, I wonder how other people do. Maybe I missed something
but this is reproducible and blocking for "real" production environements
Sorry to bump again but there have been 6 minor updates to samba package
in 16.04 LTS and since this patch is not included we still have the same
problem (fixed since 2015 on Univention bug tracker ...)
Is there any mean to help getting it included soon ?
--
You received this bug notification
** Description changed:
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
Any news on this bug ? Since it affects all versions and a tested patch exists
I thought it would have been integrated sooner (at least -proposed)
It affects production (LTS) servers running Samba + Bind which is a quite
rather common scenario on "real" environments for AD replacement. We also
** Attachment added: "Apparmor local config for bind9 + samba dlz integration"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1670450/+attachment/4832814/+files/etc_apparmor.d_usr.sbin.named
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello and thanks for taking time to look at this bug.
I have just setup a VM to test this and upgraded to zesty, all of
xenial, yakkety AND zesty behave the same and present this bug.
To test it quickly if you need to reproduce, I have only setup an AD with
"samba-tool domain provision",
Public bug reported:
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
Chromium 55.0.2883.75-0ubuntu0.16.10.1327 fixes this bug but has other video
related problems (on Twitch if you don't enable Flash explicitly like #94 or
other Flash websites even if you enable it maybe fixed on #100 but not released
yet I assume)
Why not release a Chromium 53 with CT timebomb
I suffer from the same problem with current updated libreoffice 5.1.4 on "Cape
Verde PRO [Radeon HD 7750/8740 / R7 250E"
I cannot easily recompile glamor on this box but can someone test the attached
patch from this freedesktop report and see if it fixes the problem ?
I also encounter this bug on fresh Kubuntu 15.04 install. I'm on SSD I don't
know if the daemons starting speed has somthing to do with this.
I suppose NM gets the DNS info (from DHCP), tries to notify dnsmasq. Since
dnsmasq is not yet started it launches it but I don't see any retry afterwards
12 matches
Mail list logo
