Marc Muehlfeld
2016-Oct-08 16:05 UTC
[Samba] Best Practices: Samba AD with multiple DCs/BIND9 DNS servers
Hi, Am 08.10.2016 um 16:45 schrieb PRIA IT via samba:> When running samba as an active directory controller with bind as the Dns > server and adding a secondary domain controller I have installed bind on it > as well. The wiki's basic bind configuration creates a single master bind > server with no replication so I've got two master servers and no > replication... > > Could someone please clarify how bind is supposed to be configured with > multiple ad controllers?The AD DNS zones are stored within the directory and thus Samba replicates the content, not BIND. Regards, Marc
Rowland Penny
2016-Oct-08 16:23 UTC
[Samba] Best Practices: Samba AD with multiple DCs/BIND9 DNS servers
On Sat, 8 Oct 2016 18:05:06 +0200 Marc Muehlfeld via samba <samba at lists.samba.org> wrote:> Hi, > > Am 08.10.2016 um 16:45 schrieb PRIA IT via samba: > > When running samba as an active directory controller with bind as > > the Dns server and adding a secondary domain controller I have > > installed bind on it as well. The wiki's basic bind configuration > > creates a single master bind server with no replication so I've got > > two master servers and no replication... > > > > Could someone please clarify how bind is supposed to be configured > > with multiple ad controllers? > > The AD DNS zones are stored within the directory and thus Samba > replicates the content, not BIND. > > Regards, > Marc > >This is why I couldn't understand why the OP says he has no replication. Rowland
Jason Secord
2016-Oct-08 16:31 UTC
[Samba] Best Practices: Samba AD with multiple DCs/BIND9 DNS servers
Rowland: I set up all domain controllers bind installs the same, followed the wiki. Marc: that's the piece of information i needed... Now, I'll double check this, but the other night I created a new record using the DNS snap-in from RSAT on DC1. After a few minutes i checked DC2's DNS zones and the record was not visible. I checked that drs showrepl was reporting successful replication, it was. Checked my sysvol rsync cron logs and they looked fine. How often does the DNS propagation occur? Regards, JS On Oct 8, 2016 12:06 PM, "Marc Muehlfeld via samba" <samba at lists.samba.org> wrote:> Hi, > > Am 08.10.2016 um 16:45 schrieb PRIA IT via samba: > > When running samba as an active directory controller with bind as the Dns > > server and adding a secondary domain controller I have installed bind on > it > > as well. The wiki's basic bind configuration creates a single master > bind > > server with no replication so I've got two master servers and no > > replication... > > > > Could someone please clarify how bind is supposed to be configured with > > multiple ad controllers? > > The AD DNS zones are stored within the directory and thus Samba > replicates the content, not BIND. > > Regards, > Marc > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Rowland Penny
2016-Oct-08 16:37 UTC
[Samba] Best Practices: Samba AD with multiple DCs/BIND9 DNS servers
On Sat, 8 Oct 2016 12:31:33 -0400 Jason Secord via samba <samba at lists.samba.org> wrote:> Rowland: I set up all domain controllers bind installs the same, > followed the wiki. > > Marc: that's the piece of information i needed... Now, I'll double > check this, but the other night I created a new record using the DNS > snap-in from RSAT on DC1. After a few minutes i checked DC2's DNS > zones and the record was not visible. I checked that drs showrepl > was reporting successful replication, it was. Checked my sysvol > rsync cron logs and they looked fine. > > How often does the DNS propagation occur? > > Regards, > > JSWhat OS is DC1 ? Same goes for DC2 Rowland
Maybe Matching Threads
- Best Practices: Samba AD with multiple DCs/BIND9 DNS servers
- Best Practices: Samba AD with multiple DCs/BIND9 DNS servers
- Domain Member Server: Domain Users cannot access shares
- Domain Member Server: Domain Users cannot access shares
- Domain Member Server: Domain Users cannot access shares