Hacker News Reader

Agreed. A better solution is to have all nameservers always return 2 A records in response to queries for a specific domain name. That way the browser will itself be responsible for trying to connect to each of the IPs to determine which one is alive (then with DNS pinning it will stick to the working one). And it does not matter if an intermediate DNS caching resolver ignores the TTL.

Of course the ultimate solution for HA is to implement anycast with BGP...

View on HN

Hi mrb, this is just the first release. Mammatus will return 2 A records if the endpoint domain does, so that will be built in. Of course anycast is a great option if the organisation has the option of getting an ASN, running BGP, etc. If that is not an option, Mammatus is a reasonable alternative.

One ASN is not enough. Think of the "routing mistakes" caused by censorshop etc. Or if your IGP routing blows up….

So if you really need to archive 99.999999% you'll have to invest A LOT of money, time, people.

Oh good. I read the Mammatus overview and from the resolve=self option I was under the impression it was returning only 1 A record.

Right, there is also resolve=endpoint, i.e., the "Running Dog Lackey" configuration. And others will also be possible.

Reply on news.ycombinator.com