Route53 can get expensive for lots of domains. Queries are cheap with the first 1M free, but if you have 1000 domains you’ll pay $500/month.
You can build dedicated servers in multiple AZs and data centers able to handle that many domains for far less. You might also consider running dedicated servers in each of AWS and Azure to avoid a single-provider failure. On Aug 12, 2016, at 9:44 AM, John Kinsella <j...@thrashyour.com<mailto:j...@thrashyour.com>> wrote: Also a big fan of DNS Made easy, but I wish they’d add DNSSEC already. I’m happy with AWS - one thing to consider is model out the network costs. That seems to get some people, who just expect the bill for instances at end of month. If you’re worried about availability due to an availability zone going down, ensure you have the service replicated across multiple AZs or regions and It might be worth a few minutes pondering just using Amazon’s Route53 instead of running the DNS server yourself. I haven’t looked at how the cost compares. On Aug 12, 2016, at 6:41 AM, Peter Beckman <beck...@angryox.com<mailto:beck...@angryox.com>> wrote: I highly recommend DNS Made Easy. Super fast, extremely reliable (100% up time in the last 10-12 years excluding an 8 hour period 4-5 years ago where they got DDOSed, no issues since), very affordable. #2 fastest for July: http://www.solvedns.com/dns-comparison/2016/07 Has been #1 several months this year. Beckman On Fri, 12 Aug 2016, Ryan Finnesey wrote: We need to provide DNS services for domains we offer as a registrar. We were discussing internally the different options for the deployment. Does anyone see a down side to using IaaS on AWS and Azure? We were also kicking around the idea of a PaaS offering and using Azure DNS or AWS Route 53. Cheers Ryan --------------------------------------------------------------------------- Peter Beckman Internet Guy beck...@angryox.com<mailto:beck...@angryox.com> http://www.angryox.com/ --------------------------------------------------------------------------- --- Keith Stokes
