Displaying 3 results from an estimated 3 matches for "technipages".
2020 Feb 13
3
Failover DC did not work when Main DC failed
...s pointing to a single
DC? Perhaps Bind is pointing to another internal DNS server, and then to a
public DNS?
----
Here's a way to test failover from a Windows client:
You can switch logon servers with "nltest /server:<clientcomputer>
/sc_reset:<domain\dc>"
https://www.technipages.com/windows-how-to-switch-domain-controller
So try this -- (I just did this on one of my DC's):
* Switch a Windows Client to DC4
* Verify with "nltest /dsgetdc:<domain>" and "nltest /sc_query:<domain>"
C:\WINDOWS\system32>nltest /Server:<mycomputer> /s...
2020 Feb 16
0
Failover DC did not work when Main DC failed
...NS servers as 192.168.0.218 and 192.168.0.219 and they both work as nameservers perfectly.
> Here's a way to test failover from a Windows client:
>
> You can switch logon servers with "nltest /server:<clientcomputer>
> /sc_reset:<domain\dc>"
> https://www.technipages.com/windows-how-to-switch-domain-controller
>
> So try this -- (I just did this on one of my DC's):
> * Switch a Windows Client to DC4
> * Verify with "nltest /dsgetdc:<domain>" and "nltest /sc_query:<domain>"
>
> C:\WINDOWS\system32>nltest...
2020 Feb 13
2
Failover DC did not work when Main DC failed
On 13/02/2020 16:28, Paul Littlefield wrote:
> On 13/02/2020 15:17, Rowland penny via samba wrote:
>> The various ways have already been mentioned, but are all your DCs
>> listed as nameservers (NS) in the SOA's for the forward and reverse
>> zones ?
>
>
> I think so...
>
>
> root at dc3.mydomain.com ~ $ (screen) samba-tool dns query dc3
>