There has been a lot of discussion of this topic on the list. Several things seem clear about this topic:
Each of these technologies has a certain inherent takeover speed. For example MAC address takeover is almost instantaneous (but messy), IP address takeover is a little slower and less reliable, and Dynamic DNS reconfiguration is slower yet, but has nice load-balancing properties.
For scheduled outages of things like web server cluster elements, disabling a node via Dynamic DNS an hour or so beforehand could be a useful adjunct to the other techniques. One could envison a cluster of DNS servers using IP address takeover to ensure that query server switchovers don't hang clients. MS clients don't seem to handle server switching very gracefully.
There is a software package called Fake, which has been designed to switch in backup servers on a LAN. It does most of what whatwe need for IP address takeover, but expects to be in control of the cluster, whichisn't appropriate. It has been incorporated into the heartbeat code.
NICs based on the DEC Tulip chips are especially well-suited to MAC address takeover, since they can support multiple MAC addresses on a single NIC. Otherwise, you need a spare NIC for each MAC address to be taken over.
Another class of methods for IP address takeover is discussed in the Linux Network Address Translation project web site.