Hi, I have a setup with 2 DCs which works just fine. Since we have some legacy systems which can't deal with 2 DNS Names I used ctdb to manage a floating IP (in addition to the fixed IPs) between the DCs which works great also. But then the replication breaks for some parts (Users still were replicated) because the floating IP was added to the internal DNS zone and one of the DC tried to replicate to itself after some failover tests. Can I prevent somehow that the floating IP gets added to the internal DNS zone or what could be another approach? -- Sysadmin by Nature
On 23/11/2020 15:47, Sven Wick via samba wrote:> Hi, > > I have a setup with 2 DCs > which works just fine. > > Since we have some legacy systems > which can't deal with 2 DNS Names > I used ctdb to manage a floating IP (in addition to the fixed IPs) > between the DCs which works great also.You cannot use CTDB with AD DCs If your 'legacy' system cannot deal with 2 dns names (not entirely sure what you mean by this), then just point them at one DC. Rowland
Maybe this is a stupid idea, but what we are doing here is using just the domain name for all sorts of services, i.e. LDAP. So instead of pointing a client to dc1.somedom.contoso.com or dc2.somedom.contoso.com, we point them to somedom.contoso.com which is then resolved to both and the client can pick. Best regards Johannes Am Mo., 23. Nov. 2020 um 17:02 Uhr schrieb Rowland penny via samba < samba at lists.samba.org>:> On 23/11/2020 15:47, Sven Wick via samba wrote: > > Hi, > > > > I have a setup with 2 DCs > > which works just fine. > > > > Since we have some legacy systems > > which can't deal with 2 DNS Names > > I used ctdb to manage a floating IP (in addition to the fixed IPs) > > between the DCs which works great also. > You cannot use CTDB with AD DCs > > If your 'legacy' system cannot deal with 2 dns names (not entirely sure > what you mean by this), then just point them at one DC. > > Rowland > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: lists.samba.org/mailman/options/samba >