Domain scan config / ad authentication issue

I've noticed that the Domain Controller per domain set up in the domain scan configuration is the same DC used to authenticate the users signing in to Servicedesk (v7 build 7012).

I had an issue where a DC was taken offline (not in my domain) and we were not aware of it and users could not sign in. I changed the config to look at another DC in the affected domain and all was well once more.

My question: is it possible to configure SDP to look at more than one DC per domain, or would a 'round robin' DNS alias be a valid alternative (would this work - would it keep trying if a DC didn't respond?).

I want to avoid this happening again and provide some resiliency when one of my remote regions decides to take down the DC I'm pointing the Servicedesk at without telling me.

Cheers,

Dean