short TTL's are the key to defeating the effect of caching of records make stale by changes.I host my own primary nameserver here. My question then, is, how is the best way to handle a quick tranfer of DNS?
delegate your domains to both ISP's DNS's.
You can't have two sets of data for the same hostnames. one or the other.The backup ISP would provide us with several static IP addresses, however, all our DNS points to our current addressing scheme.
Once the primary ISP goes down, his DNS's become unreachable as do your machines on his ip's.
You'll have to have connectivity to the backup ISP and his ip's, probably your biggest logistics angle.
when you have to switch your servers' ip's to the backup ip's, then the backup DNS zone data has to be modified. Short TTL on the original DNS records will reduce the effect of caching during the switch.
My perspective is that all of the above in unnecessary unless you have servers of huge $$$ importance + traffic and need absolute 24x7 connectivity and redundancy. At which point, I have to ask why you were with such a flaky, unverifiable/unverified provider in the first place.
Although it still hurts and is no consolation, I don't think it's very common what happened to you. eg, I'm losing my SDSL provider, ip.net, but have 6 weeks notice to prepare for it.
Len
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
