This isn’t a Discourse issue per se, but perhaps people who have set up digital ocean droplets can comment. I’m trying to get the basic domain to resolve properly. The “www” domain is fine and has been operating for the past 4 months - but then I recently noticed that the bare “rapa…news” domain is not resolving. Here is what my settings look like right now. What do I need to do to get the bare domain (sans www) to resolve properly? The settings as they are configured fight now - are not working… Any help greatly appreciated! [Screen Shot 2022-02-20 at 1.49.11 PM]

You need to setup an A record for rapamycin.news as well, pointing to the IP address

Do I delete that Name record (rapamycin.news to www.rapamycin.news) that doesn’t seem to be doing anything?

Why don’t I get it when I try to access the site via my chrome browser - this is what I see: [Screen Shot 2022-02-20 at 2.21.48 PM]

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: [image] Set up Let’s Encrypt with multiple domains / redirects Sysadmins 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: [image] Non www to www without certificate error Self-hosting The easiest way is to use www.forcewww.com for that. (Disclaimer: that’s my own service)

Clearing the browser worked! Thanks so much. Problem solved!

The easy solution is forcewww.com. A harder solution is Setting up Let’s Encrypt with Multiple Domains.

Thanks Jay. Having them both pointing to the same IP address seems fine for now. I don’t anticipate the IP address changing very often, and can easily update both records when I need to.

DNS Settings for Digital Ocean Droplet - Root Domain?

Product Support Self-hosting

BCHK (Bcguy) February 20, 2022, 10:16pm 4

Ah - I couldn’t add the new A record without first deleting that CNAME record. Thanks - I hope it works! Will update in a few hours.

Topic		Replies	Views
Adding www. to Domain Self-hosting	12	1295	March 20, 2022
Correct DNS records to set when Discourse is hosted on WWW subdomain? Self-hosting	2	1271	May 9, 2020
Www.example.com OK, but example.com NOT Self-hosting	3	1212	September 4, 2019
[DigitalOcean] hostname having "www" in A records showing blank page Self-hosting hosting	22	8291	September 18, 2019
Making 'www' work with Discourse Product Support	30	3058	May 15, 2020

DNS Settings for Digital Ocean Droplet - Root Domain?

Related topics