We are doing the same thing as you on EC2, but we are using Dynamic DNS "DDNS" with a script that updates dns memcached.xxx.com with the new ip when the server boots.
checkout http://www.dnsmadeeasy.com/ & look at their DDNS and scripts. everything you want is there, cheap, simple, & it works. On Oct 6, 6:41 pm, "Edward M. Goldberg" <edwardmgoldb...@gmail.com> wrote: > I have used Memcached in EC2 now for many deployments and I am seeing > issues with DNS names used for Memcache access: > > 10.1.2.3:11211 vs. memcache.0.my-name.net:11211 > > I have set the TTL very low to provide for fail over from one server > to the next, when new instances are launched. > > Does anyone have ideas on how I can get the same "Fail Over" I enjoy > from DNS? > > What do you see as the "impact" of DNS look ups on Memcache service? > > I see /etc/hosts as one solution that keeps the code the same. But > updates are hard to distribute... > > What are your thoughts, solutions? > > Edward M. Goldberghttp://myCloudWatcher.com/
