# Installing over DigitalOcean and Namecheap?

**URL:** <https://meta.discourse.org/t/installing-over-digitalocean-and-namecheap/95598>\
**Category:** Self-hosting\
**Created:** [24.Август.2018 20:01:24 UTC](https://meta.discourse.org/t/installing-over-digitalocean-and-namecheap/95598 "2018-08-24T20:01:24Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [28.Август.2018 00:34:43 UTC](https://meta.discourse.org/t/installing-over-digitalocean-and-namecheap/95598/5 "2018-08-28T00:34:43Z")

</div>

I’m scratching my head on this one, moving DNS only makes sense if it gives you something extra. DigitalOcean really doesn’t.

> [@pfaffman](#):
>
> And some stat I saw someone showed that they had very fast resolution times

That’s a meaningless metric. Once cached, DNS performance is down to your local instance, only expiring when the TTL demands, it and that’s really the key factor here, particularly when deploying a new instance or moving a site for the purpose of DR.

The default TTL at DO is 3600 seconds - a whole hour. You can set it to less, but most users won’t. That’s pretty horrible even compared to the likes of NameCheap (1800 seconds) and GoDaddy (600 seconds).

As Jeff mentioned, CloudFlare has disrupted the space significantly, their default TTL of 300 (5 minutes) makes a massive difference when deploying or troubleshooting DNS - it’s night and day. [They offer an API too](https://support.cloudflare.com/hc/en-us/articles/360000841472-Adding-Multiple-Sites-to-Cloudflare-via-Automation).

---

_[View the full topic](https://meta.discourse.org/t/installing-over-digitalocean-and-namecheap/95598)._