30
Adding additional FreeDNS domain to duckdns (nginx/certbot) (lemmy.world)
submitted 1 year ago by to c/selfhosted@lemmy.world
5 comments fedilink hide all child comments
 

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!

all 5 comments

sorted by: hot top controversial new old
[–] 4 points 1 year ago

It wouldn’t be any different than your current configuration other than the domain itself.

  • permalink
  • fedilink
  • source
    •
    [–] 2 points 1 year 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.

  • permalink
  • fedilink
  • source
    •
    [–] 1 point 1 year ago (2 children)

    Assuming I understood your scenario, Canonical name record pointing one DNS name to another domain, then recreate your letsencrypt on the host.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •