
September 7th, 2012, 11:10 AM
|
 |
Automagically Delicious
|
|
Join Date: May 2004
Location: 127.0.0.2 - I live next door.
|
|
|
The best way is to have a physical Load balancer. What this does is creates a "Virtual IP Address" that's shared for a pool of servers. So let's say the VIP is 192.168.1.5 but the "Real IP"s are 192.168.100.5, 192.168.100.6. You set your DNS entries up for the 192.168.1.5 and the traffic flows to the LB and it then distributes the load based on rules you've defined. E.g. round-robin, last-used, etc.
I forget what the setting is, but there's a registry entry for Windows servers that allows for non-strict naming. Basically there's an issue where if you point to server.test.com and the LB sends you to server01.test.com; the actual "server01" won't recognize the other name even though the connection's come in correctly. Easy fix though and we do it here all the time.
__________________
Adam TT
|