4 ms·
After being with Dyn for 8+ years, this last week I moved from them to Amazon. The Dyn interface is chaotic - so bad I contemplated just reverting to hosting D
by ecaron 14y ago
After being with Dyn for 8+ years, this last week I moved from them to Amazon. The Dyn interface is chaotic - so bad I contemplated just reverting to hosting DNS myself in PowerDNS/Poweradmin (https://www.poweradmin.org/trac/ https://www.poweradmin.org/trac/).
I never had downtime issues with Dyn, and the performance was satisfactory. But I tried talking a coworker through updating our TXT/SPF record and told him he'd have to "stumble around until he found the right interface" - at that point I realized we deserved better.
- davidgerard 14y agoThe unbelievably terrible interface was a major factor in us moving our stuff from Netnames to Amazon. Amazon Route53 is just ridiculously easy to use. Also, machine-controllable. Not as good as shadow primary, but second-best option and saves us so much frustration just doing stuff. Though if there were someone who was as non-sucky to use as Amazon, I'd be interested too.
- donavanm 14y agoIf you really want AXFR check out Route53d http://code.google.com/p/route53d/ http://code.google.com/p/route53d/. Acts as an AXFR to route53 API proxy. The route 53 sample code also has import/export to bind zone file format.