Im switchting now to IPX or FrontRageHosting.... by the way FrontRage offers free DNS service via SolusVM

FREE DNS Management - with DNS servers in 4 geographically diverse locations on 4 different network providers (No need for extra ip's or other VPS's for your DNS, it's managed through our client porta

DNS order of A records is a bit problematic.

Just specify multiple DNS entries and the one who does the actual DNS lookup while look which one pings back fastest and uses that.

I've done exactly what is proposed here with DNSMADEEASY. $50 a year roughly for our use and DNS total lookups.

Anyone have an IP/DNS of one of Hulu's content servers in the US?

What you need is a dns product like GSLB if you deploy the servers acrossing the IDCs.

Round robin DNS is blah. It's DNS solution 101. Has limitations and inefficiencies.

Cheap is rolling your own VPS collection out with geographic DNS. (Finding DNS provider with GeoDNS capability at low price is the biggest part of the solution).

* setup round robin DNS with cross failover

(Quote)

maybe a dns server with a script to verify availability (pinging or connecting to a port) and change the IP if needed?

Use those dns based solutions that redirect based on availability, usually not free though.

* Set the DNS servers to have to A records with different TTL (is this possible?), so if the primary goes down, it will redirect to the backup

It was a DNS issue and I've resolved it now. We were hit with a large UDP flood yesterday and I had to reconfigure our DNS to avoid future issues.

Distributed content + geoip based dns redirection using couple of vps in different location can help a lot.

Yeah I have issues where a few websites refuse to load (usually connect.facebook.net and twitter and most CDNs) and yeah I did set ms-dns servers!

* EDIT: Forgot to mention, also need reverse DNS delegation for at least IPv6

yes, we just need to change/add an AAAA record in DNS,

@gbshouse @DNSbed : I'd like to draw on your DNS expertise if that's OK. Particularly for error checking... for record submissions that are DNS-illegal. For example, I know that I shouldn't allow a CN