DNS Services for a registrar

• Subject: DNS Services for a registrar
• From: bill at herrin.us (William Herrin)
• Date: Fri, 12 Aug 2016 11:33:59 -0400
• In-reply-to: <BLUPR05MB595[email protected]>
• References: <BLUPR05MB595[email protected]>

On Fri, Aug 12, 2016 at 1:56 AM, Ryan Finnesey <ryan at finnesey.com> wrote:
>  Does anyone see a down side to using IaaS on AWS and Azure [for DNS]?

Latency is critical for DNS. Literally everything else an application
does stalls behind completion of the DNS lookups.

Everything else being equal, virtuallized infrastructure will always
exhibit higher latency than bare metal. Always.

> We were also kicking around the idea of a PaaS offering and using Azure DNS or AWS Route 53.

I don't know their implementations well. I would hope they run the
underlying DNS servers on bare metal rather than leveraging their VM
infrastructure. I would worry that they offer all sorts of extra
features which are -single source-. If you pick Route 53 and your
customers get used to those features you may find yourself locked in
at Amazon's mercy.

Regards,
Bill Herrin


-- 
William Herrin ................ herrin at dirtside.com  bill at herrin.us
Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/>

• References:
  • DNS Services for a registrar
    • From: ryan at finnesey.com (Ryan Finnesey)

• Prev by Date: DNS Services for a registrar
• Next by Date: DNS Services for a registrar
• Previous by thread: DNS Services for a registrar
• Next by thread: DNS Services for a registrar
• Index(es):
  • Date
  • Thread