Displaying 3 results from an estimated 3 matches for "yourprimary".
Did you mean:
your_primary
2020 Feb 12
0
Failover DC did not work when Main DC failed
...nf
> search mydomain.com
> nameserver 192.168.0.218
>
>
> ...should I have THIS instead?
Yes, thats much better.
Now, the order here of nameserver can influence things also.
So, order of nameserver "AFTER" a EXTRA AD-DC joined the domain.
Per example.
#DC3.
search yourprimary.dnsdomain.com other.important-domains.tld
nameserver 192.168.0.218 #DC3 ( new extry after the join of the AD-DC )
nameserver 192.168.0.219 #DC4 ( first entry before and when your domain Joining and AD-DC )
options timeout:2
options attempts:3
options rotate
#DC4.
search yourprimary.dnsdomain....
2020 Feb 12
4
Failover DC did not work when Main DC failed
What do you see/get when you run:
dig NS $(hostname -d)
With 2 dc's you should see 2 records.
In the past this was a bug at samba joins so only 1 NS record existed.
Worth to have a look at.
And adding this to /etc/resolv.conf:
options timeout:2
options attempts:3
options rotate
Also might help.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba
2020 Feb 12
2
Failover DC did not work when Main DC failed
...r 192.168.0.218
>>
>>
>> ...should I have THIS instead?
> Yes, thats much better.
>
> Now, the order here of nameserver can influence things also.
> So, order of nameserver "AFTER" a EXTRA AD-DC joined the domain.
> Per example.
>
> #DC3.
> search yourprimary.dnsdomain.com other.important-domains.tld
> nameserver 192.168.0.218 #DC3 ( new extry after the join of the AD-DC )
> nameserver 192.168.0.219 #DC4 ( first entry before and when your domain Joining and AD-DC )
> options timeout:2
> options attempts:3
> options rotate
>
> #DC4...