If DCs returned by AD Site are offline, Nomad crashes
In the event that all DCs offered by an AD Site lookup are offline, Nomad shouldn't crash.
I know, I know, DNS should not be offering DCs that are down, but in the catastrophic event that an entire DC is suddenly offline, and the SRV lookup gives an AD Site that lists only these DCs, Nomad should gracefully handle that circumstance, instead of crashing.
2018-02-21 09:56:43.759 NoMAD[29039:1952175] level: info - Trying host: ***.***.com
2018-02-21 09:56:48.969 NoMAD[29039:1952175] level: info - Server is dead by way of socket test: ***.***.com
2018-02-21 09:56:48.969 NoMAD[29039:1952175] level: base - All DCs in are dead! You should really fix this.
2018-02-21 09:56:48.969 NoMAD[29039:1952175] level: debug - Resetting default naming context to: DC=***,DC=***
2018-02-21 09:56:48.969 NoMAD[29039:1952175] level: base - Not connected to the network
2018-02-21 09:56:48.969 NoMAD[29039:1952175] level: base - Logged in.
2018-02-21 09:56:48.998 NoMAD[29039:1952175] level: base - Auto-login not attempted.
2018-02-21 09:56:48.998 NoMAD[29039:1952175] level: debug - Starting Cert clean
2018-02-21 09:56:48.998 NoMAD[29039:1952175] level: debug - Beginning cert clean.
2018-02-21 09:56:49.032 NoMAD[29039:1952175] level: debug - Certificate NT Principal: ***@***.com
2018-02-21 09:56:49.032 NoMAD[29039:1952175] level: debug - Found cert match
Illegal instruction: 4
Edited by Joseph Chilcote