PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 8.8.8.8,dhcp-option DNS 4.2.2.1,route 10.2.0.0 255.255.255.0,redirect-gateway def1,route 10.2.0.1,topology net30,ping 10,ping-restart 120,if

Sat Apr 19 00:48:43 2014 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.0.35.1,topology net30,ping 10,ping-restart 120,ifconfig 10.0.35.6 10.0.35.

SolusVM Control Panel2048mb Ram50gb RAID-10 HDD (100% SSD in LA!)2TB Bandwidth100mbps Port Speed1 IPv4 AddressvSwap EnabledFull ControlOne-Click OS Reloads99.9% Uptime Guarantee24/7 SupportReverse-DNS

@neroux so i just need to buy the "backends" server , open a port then i add then DNS A records on the backends to point to the main server just as @ben78 said and it will be done

Why would you think you would need to set it up on each of them? You dont even need to set it up on the main/front server but you only need to have any valid DNS server pointing to it.

Your DNS IN A must point to the main server and the server will send your request to the backends.

@NameStuff - do you have any contact with them? or can provide us source of

@gbshouse Baidu has been trying to build their anycast DNS, and they want the anycast networks. You may contact with them for a potential biz corps.

*DNS Configuration

I can provide the daemon system and an API (I play fine on it).

for whm/cpanel - build a service like whmdnsonly that replicates your server with mysql in readonly and in the event of an outage you can trigger a DNS update to whmdnsonly. the rollback would have t

you dont need/use tiny TTL. when you add multiple A records for the same dns name they get handed out in order. record 1, record 2, record 3, record1, record2, record3 etc. if you are dealing with 300

fortunately i have a LEB running cpanel dnsonly so all the dns is still working for these customers and only 4 of them use email off this server...

Very unscientific analysis because I've never done it. You can also combine these methods with in-server redirects, as linked above, to foolproof even in the case of DNS caching.

None of the dns trick could do such algorithm, it is on the server (dns++) side.

In all my experience I have never found a way to do this with DNS, there is no way the client would know to switch servers, it would just start failing to be able to connect. Best case scenario, if y

Webhooks with Rage4 will do this, but DNS caching on client or ISP-side may work against you in this sort of situation as stated above.

Will be much harder to do with DNS alone, even using tiny TTLs. You could try removing from the round robin once it nears capacity but there's no guarantee some clients won't still see it as not every

@udk I would prefer doing that at dns level. I want to embed a player to several websites thru a single http code that can be changed by me without having to be able to access those websites (they are

I think your best bet is not using DNS round robin at all and doing it all the application level. A simple script to determine resource usage and redirect users to available server should suffice. Thi