[Release Planning 4.2] Samba 4.2.0rc1 scheduled for Wednesday, October 1
Martinx - ジェームズ
thiagocmartinsc at gmail.com
Wed Sep 24 20:49:29 MDT 2014
I'm being affected by BUG 10595, it is a serious issue.
Also, the following BUGs needs to be addressed quickly, if possible, I
hope, at least, for 4.2.X (or 4.3, by blocking
* Samba has a wrong "Dual-Stack" implementation
* samba_dnsupdate does not add/update/remove NS records
Currently, because of 10729, I can not enable IPv6 in any of my `Samba4 AD
DCs`, because there are in my network, others *perpetual* IPv4-Only `Samba4
AD DC` (located within AWS EC2, small offices, etc), so, if I enable IPv6
in one of my Samba4 DCs, then, it will trigger lots of errors on all
remaining DCs. Also, it becomes impossible to join (samba-tool domain join
... ) a brand new IPv4-Only Samba4 as a DC (the following instructions:
https://wiki.samba.org/index.php/Join_a_domain_as_a_DC - doesn't work in a
mixed environment, where you have a Dual-Stacked Samba4 AD DC ("master"),
and tries to add an IPv4-Only DC.
And about 10810, the lack of a secondary NS, brings a problem for you to
use your couple "samba4 + bind9" to publish "authoritative domains" to the
Internet. Am I right?! :-)
On 22 September 2014 16:15, Marc Muehlfeld <mmuehlfeld at samba.org> wrote:
> Am 22.09.2014 um 20:58 schrieb Karolin Seeger:
> > Samba 4.2.0rc1 will be delayed. Some important things need to be
> > discussed/finished first (CTDB releases e.g.).
> > The new planned release date is Wednesday, October 1.
> > has been updated accordingly.
> > If you are aware of any other issues, please let me know asap!
> How big is the chance that the following two bugs are getting fixed in 4.2?
> * Demote a permanently offline DC with ADUC fails:
> (Note: It's not possible to demote a broken DC with samba-tool
> yet. So no way to get the broken DC out of the domain.)
> * Transfering roles to other DC on the domain is succesfully,
> but demoting the previous owner of the roles fails
> We have quite often people on the mailing list with a broken DC, that
> can't be demoted any more. And also the problem that a working DC should
> be demoted, but the FSMO roles are not transfered clean to the new one.
> In both cases, it's not possible to get the DC out of the domain. And
> because there is currently not way, the people start editing the AD
> manually, even if we advice against, because it can cause serious problems.
> It would be really great if this two would be fixed. I think they are
> very serious.
More information about the samba-technical