Adding additional FreeDNS domain to duckdns (nginx/certbot)

Submitted ⁨⁨6⁩ ⁨days⁩ ago⁩ by ⁨iturnedintoanewt@lemmy.world⁩ to ⁨selfhosted@lemmy.world⁩

Hi guys!

I’m a bit…frustrated with the inconsistencies of duckdns.org. Don’t take me wrong, I seriously appreciate the easiness and the free service they have provided over the years. But I’m considering to have a second account with FreeDNS. How would I add it to my servers? The main one is a nginx server with certbot, that serves the current myserver1, myserver2, myserver3.mydomain.duckdns.org urls. Once registered mydomain.afraid.org, what changes should I do to make nginx serve also the new myserver1.mydomain.afraid.org and so on?

Thanks!

source

Comments

Sort:hotnew top

undefined@lemmy.hogru.ch ⁨6⁩ ⁨days⁩ ago
It wouldn’t be any different than your current configuration other than the domain itself.

source
purplemonkeymad@programming.dev ⁨4⁩ ⁨days⁩ ago
Pretty much, add the new domain to certbot, then create a new server directive with the new name and certificate paths. I would probably just copy and paste the existing one for your current domain, then just change the domain. SNI will then select the right certificate for you.

You can set certbot to create a single certificate with both domains, but tbh the above is just simpler to setup and maintain.

source
non_burglar@lemmy.world ⁨6⁩ ⁨days⁩ ago
Assuming I understood your scenario, Canonical name record pointing one DNS name to another domain, then recreate your letsencrypt on the host.

source
- iturnedintoanewt@lemmy.world ⁨4⁩ ⁨days⁩ ago
  Recreate? Sorry but what about the old one? I’m not ready to turn the old one off just yet, I’d like both to be active.
  
  source
  - non_burglar@lemmy.world ⁨4⁩ ⁨days⁩ ago
    You can create a canonical name (CNAME) record to point to your old domain, you don’t need to recreate the LE if you don’t want to.
    
    source