Well that exists with gdnsd, at least for HTTP.

@raindog308 Hehe that would be nice, a DNS server with built in HA, failover, heartbeat and of course it supports all possible protocols to failover (Image)

Your browser or on windows your dns cache will choose one the first time you dns the domain. If its unable to connect it will usually go to the second. Occasionally you will have to wait for ttl to

Yeah, change DNS only, dont worry about TTL, it will change when will change, 30 days are more than enough. Round-robin means seting up more IPs for load balancing usually. From your page I see you kn

if they let the 2 IPs stay for 30 days, don't worry about dns propagation. just change to the new one and let the traffic with the old IP cached hit the old IP until the ttl expires.

Hi all, I've been playing around with DNS, but for some reason, can't seem to resolve what I'm aiming for.

I dont think the links contain IP, they shouldnt. It should work only with DNS change.

...which most DNS nameservers do not honor, alas.

Probably not, I do remote mysql connections when moving shared hosting sites between LA and Charlotte so both copies of the site are using a single copy of the database, and most of the time these are

* Before the change, set the TTL in the DNS of the domains to 1 hour instead of 1 day.

I want to use an L2TP/IPsec VPN while I'm at university to get a fixed IP, some more privacy and speed up DNS resolution.

* well, while I'm up, setup DNS entry for new host

Oddly enough it is however faster through a VPN as the DNS resolution is slow and they won't let you use different DNS servers.

Namely, Internet Exporer. Microsoft email clients are also really freaking bad for this. Outlook, Outlook Express, Whatever-they-call-it-now are horrible with DNS. Basically they resolve at start-up a

Lots of DNS services don't honor short TTLs like that. Many don't honor times less than one hour.

@NanoG6 DNS Failover is easy and cheap to do, the problem is that the majority of our clients use IPs and not DNS for their needs. If they were using DNS they could have a failover setup like we have

As said above, you could do DNS, Static webpages with nginx.. PHP is possible as well (Image)

From what I've seen, the majority of our clients that have them use them for DNS, VPNs, testing scripts, and learning (the beauty of linux is you only need about 12MB to play around with command line

Yes, anyway, as they said, are 6 hours of downtime... I wonder if they will give us our IPs before the move. Otherwise, are 6 hours plus DNS propagation =/

That's how I read it too. Only thing I can think to do is lower DNS TTLs now and monitor for the new IP becoming reachable.