# DNS Settings for Digital Ocean Droplet - Root Domain?

**URL:** https://meta.discourse.org/t/dns-settings-for-digital-ocean-droplet-root-domain/218903
**Category:** Self-hosting
**Created:** [February 20, 2022, 9:52pm UTC](https://meta.discourse.org/t/dns-settings-for-digital-ocean-droplet-root-domain/218903 "2022-02-20T21:52:08Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [February 20, 2022, 10:36pm UTC](https://meta.discourse.org/t/dns-settings-for-digital-ocean-droplet-root-domain/218903/8 "2022-02-20T22:36:27Z")

</div>

If clearing your browser cache doesn’t work, it may be because you need a letsencrypt certificate to cover the non-www version.

There’s a bit of info on how to do that in this topic:

> [@Set up Let’s Encrypt with multiple domains / redirects](https://meta.discourse.org/t/setting-up-let-s-encrypt-with-multiple-domains/56685):
>
> NOTE: @pfaffman says: This page needs to be cleaned up. There is now a new ENV setting that will let you add more hostnames. In your app.yml under your DISCOURSE\_HOSTNAME line (it can go many places but that one makes sense), add DISCOURSE\_HOSTNAME\_ALIASES: domain.com,other.domain.com and early reports suggest that you’ll get valid certs for those domains and that accessing https://domain.com will properly redirect you to your DISCOURSE\_HOSTNAME without a certificate error. If you do that an…

Or I think you can use something like this instead:

> [@Non www to www without certificate error](https://meta.discourse.org/t/non-www-to-www-without-certificate-error/215022/5):
>
> The easiest way is to use [www.forcewww.com](http://www.forcewww.com) for that. (Disclaimer: that’s my own service)

---

_[View the full topic](https://meta.discourse.org/t/dns-settings-for-digital-ocean-droplet-root-domain/218903)._