Dear all, as I am currently planning a network with Samba AD DC I was wondering if you can recommend any best practice for a multi-homed AD DC. My current plan is to have one NIC for Samba services and a second one dedicated to management functions (e.g. SSH) on a separate network restricted to admin users. In a testbed scenario I already discovered that once both adapters exist, samba seems to automatically create A/ AAAA records in DNS for both interfaces which does not seem useful to me in this context. Hence my question: Do you have any best practice/ recommendation for or against such a scenario? Any suggestions are highly appreciated. Best regards Johannes
On 17/05/2020 19:30, Johannes Engel via samba wrote:> Dear all, > > as I am currently planning a network with Samba AD DC I was wondering if > you can recommend any best practice for a multi-homed AD DC.Best practise is: do not multi-home a DC. Rowland
On Sun, May 17, 2020 at 1:43 PM Rowland penny via samba < samba at lists.samba.org> wrote:> On 17/05/2020 19:30, Johannes Engel via samba wrote: > > Dear all, > > > > as I am currently planning a network with Samba AD DC I was wondering if > > you can recommend any best practice for a multi-homed AD DC. > > Best practise is: do not multi-home a DC. > > Rowland > >Why?