←back to thread

How when AWS was down, we were not

(authress.io)
203 points mooreds | 1 comments | 17 Nov 25 17:07 UTC | HN request time: 0.217s | source
Show context
indigodaddy ◴[17 Nov 25 19:26 UTC] No.45957168[source]▶
Back in the day (10-12 years ago) at a telecom/cable we accomplished this with F5 Big IP GSLB DNS (and later migrated to A10's GSLB equivalent devices) as the auth DNS server for services/zones that required or were suitable for HA. (I can't totally remember but I'm guessing we must have had a pretty low TTL for this).

Had no idea that Route 53 had this sort of functionality

replies(2): >>45958026 #>>45958537 #
indigodaddy ◴[17 Nov 25 21:28 UTC] No.45958537[source]▶
Speaking of F5 Big IP DNS devices, does anyone know of any auth DNS software solution for GSLB/health checking for DNS (I guess excluding Route 53 or other cloud/SaaS). Last I looked all I could find was the polaris-gslb addon for PowerDNS, but the GitHub for that has no activity in 8 years.
replies(1): >>45964023 #
1. loadbalancer ◴[18 Nov 25 11:53 UTC] No.45964023[source]▶
We've been using Polaris for the Loadbalancer.org GSLB for a few years now, and we've found it fast and stable. Its so simple its never needed any updates:

https://www.loadbalancer.org/blog/gslb-why-global-server-loa...

Although we did patch a dynamic health check a while back, which will be open source of course. But I'll get someone to check if we actually gave it back to the community or not...