[Samba] Failover DC did not work when Main DC failed

[Kris Lou]

Is DC4 listed in in an A record for your mycompany.com?

Do logs show that it's answering requests during the course of a normal
workday?

If so ... time to simulate DC3 failure, I guess.

Kris Lou
klou at themusiclink.net


On Tue, Feb 11, 2020 at 5:25 AM Paul Littlefield <info at paully.co.uk> wrote:

> On 03/02/2020 18:49, Kris Lou via samba wrote:
> >
> > From windows:
> > echo %logonserver%
>
> \\DC3
>
>
> > nltest /dsgetdc:<domain>
>
> DC:\\DC3
> Address: \\192.168.0.218
> Dom Guid: bla bla bla
> ...
> The command completed successfully.
>
>
> >  From a *nix domain member (i.e. client, not DC):
> > wbinfo --getdcname=<domain>
> > winbind --ping-dc
>
> wbinfo --getdcname=MYDOMAIN
> DC3
>
> wbinfo --ping-dc
> checking the NETLOGON for domain[mydomain] dc connection to "
> dc3.mydomain.com" succeeded
>
>
> > That's probably expected.  I don't think nslookup can query multiple DNS
> > servers at once.  But is DC4 actually responding to DNS queries?  Compare
> > "nslookup <domain> <DC3-ip>" and "nslookup <domain> <DC4-ip>", which will
> > hopefully tell you that both DC3/DC4 are capable of answering queries.
>
> Yep, DC4 is responding to queries.
>
>
> > This DNS timeout on "standard traffic" is probably what you need to
> figure
> > out then.
>
> OK.
>
>
> > And I hate to ask, but are both samba and bind set to automatically start
> > after boot (on the DC's)?
>
> Yup.
>
> Paully
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>