DNS Services for a registrar

Fri Aug 12 14:43:21 UTC 2016

>From the speed comparison report: "Averaged across all name servers"

That's a silly, synthetic, and non-representative test. It encourages
cohosting all your NS at all your sites to game the performance numbers,
hurting availability.
I'd expect to see a decent amount of latency variance across the NS in a
given delegation because I want them to get anycasted to different
transit/physical locations, and I would also expect that not to translate
into notable user-perceived latency due to resolver's server selection
logic.

-eli

On Fri, Aug 12, 2016 at 9:41 AM, Peter Beckman <beckman at 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
> beckman at angryox.com
> http://www.angryox.com/
> ------------------------------------------------------------
> ---------------
>