[Samba] [samba-newsletter] New Enterprise Samba 4.1.11 Packages Available for Download | was: Re: problems after lowering tombstone...

[mourik jan heupink - merit]

Just to follow up on this older thread:

The below had escaped my attention, so I'm reposting it... There has 
been a lot of discussion lately on the subject of dns tombstone 
lifetime, and DC=DOMAINDNSZONES,*.ldb growing insanely.

(I had noticed but did not understand that, in a test setup, the first 
time starting sernet-samba-ad-4.1.11 took very long indeed. (yes: hours, 
in  a i5 kvm machine)
Anyway: Apologies for reposting if you already knew about this...)

Regards, and I would like to say: Thank you all for your kind help over 
the last period of time. This list has some incredibly knowledgeble and 
helpful people! Some that come to mind: steve, achim, rowland, marc, 
louis: thank you, I have learned a lot from just reading your posts.

Mourik Jan

-------- Original Message --------
Subject: [samba-newsletter] New Enterprise Samba 4.1.11 Packages 
Available for Download
Date: Tue, 19 Aug 2014 15:14:45 +0200
From: SerNet Samba Team <samba at sernet.de>
Reply-To: samba at sernet.de
Organisation: SerNet GmbH, Goettingen, Germany
To: samba-newsletter at sernet.de

<snip>

   * Partial fix for bug #10749 - Support for DNS_TYPE_TOMBSTONE records.
     DNS_TYPE_TOMBSTONE records are created, but not periodically 
cleaned up.
     The cleanup task will be added in future releases.
     As DNS tombstone records will now be recycled automatically,
     this fix will prevent 
/var/lib/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,*.ldb
     from growing significantly over time.

Note:

   If you upgrade an active directory domain controller
   from a version prior to 4.1.10 to Samba 4.1.10 or newer,
   please note that it can take samba several minutes
   (or even hours in very large installations) to complete
   startup due to a re-indexing of the AD database.

   In a multi-DC setup, be sure to update the DCs one
   after another, waiting for one DC to be fully up and
   running again before updating the next one.