# Installation sur DigitalOcean et Namecheap ?

**URL:** <https://meta.discourse.org/t/installing-over-digitalocean-and-namecheap/95598>\
**Category:** Self-hosting\
**Created:** [Août 24, 2018, 8:01 UTC](https://meta.discourse.org/t/installing-over-digitalocean-and-namecheap/95598 "2018-08-24T20:01:24Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [Août 28, 2018, 10:57 UTC](https://meta.discourse.org/t/installing-over-digitalocean-and-namecheap/95598/8 "2018-08-28T22:57:51Z")

</div>

> [@pfaffman](#):
>
> I think that’s true, but I saw one article (which I won’t try to find) that indicated that the resolution times for Digital Ocean were really good.

You’re talking about a single record which will be orders of magnitide lower than the TTFB. There’s really no reason this should influence who hosts DNS with modern infrastructure.

> [@pfaffman](#):
>
> Adding the records to Digital Ocean’s name servers doesn’t hurt (since nothing will be looking there) and it does keep anyone else from using Digital Ocean’s name servers for their domain.

I’m sorry, what? At first I wondered if you meant it _doesn’t_ keep anyone else from using DO nameservers for their domain, but re-reading it’s not what you said…

> [@pfaffman](#):
>
> Reducing TTL seems to be a big win only if you expect DNS to be changing often. . .

That suggests a fundamental lack of understanding of TTL - it might be easier to think about it as caching. After an update, clients which haven’t requested it since the last TTL window server will resolve it immediately. In the case of DO and their 3600 second TTL, a DNS server which requested the record 60 seconds prior would be **59 minutes behind on the change**. To users that’s ~an hour of downtime.

Compare that to the default TTL at Cloudflare, where the **maximum** blip due to DNS propagation is going to be five whole minutes.

It’s not a question of changing DNS frequently, it’s about adding a huge unnecessary delay that impacts service. You’ll encounter it in any migration whether they’re planned _or otherwise._

On the note of Cloudflare I did compare their DNS performance to DO briefly and consult DNSPerf, they’re a good third quicker in most cases- but as I said it’s a meaningless metric.

---

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