Jump to content
|Topic||Stats||Last action by|
|What to do with the pins on the back of the I/O motherboard shield?||
|Google now lets you download your data from Gmail, Google Calendar||
|Controversy over Fisher-Price baby Apptivity Seat||
|Gran Turismo 6 microtransaction pricing revealed - £120 for a Jaguar XJ13||
|Car tax disc to be axed after 93 years||
Posted 16 November 2012 - 21:16
Posted 16 November 2012 - 21:39
Posted 16 November 2012 - 22:05
Posted 17 November 2012 - 06:26
Posted 17 November 2012 - 11:43
Posted 17 November 2012 - 13:19
It achieves the same effect. The second server must be up and running in order to provide fall-over, why not use it and load balance as well.
That is NOT WHAT he asked at all!! That is simple round robin, 1 time get this address, next time get that address.
You can load balance that way - not failover!
"which will always point to server1.domain.local but in the event that server is down points to server2.domain.local"
Posted 17 November 2012 - 13:40
Posted 17 November 2012 - 14:47
Posted 17 November 2012 - 20:11
Posted 17 November 2012 - 20:50
Posted 05 May 2013 - 16:08
There is nothing in MS dns to do that - like I said you would need some script or software to monitor the systems and then change the dns record. You could modify the script I linked to do what you want. MS dns might a bit more difficult to work with than bind.
Posted 05 May 2013 - 22:31