Two dynamic DNS services - to one server

[xrapidx]

Not sure where to post this.

I'm hosting my home server with various services in docker, one of them being home-assistant as a subdomain: homeassistant.<mydomain>.duckdns.org

SSL/Reverse Proxy is done using this container: https://hub.docker.com/r/linuxserver/letsencrypt/

What I'd like to do is have a second dynamic dns domain service access home-assistant on a different url, basically <mydomain>.<service>.com

Anyone know if this is possible somehow?

 

[SauRoNZA]

Not sure where to post this.

I'm hosting my home server with various services in docker, one of them being home-assistant as a subdomain: homeassistant..duckdns.org

SSL/Reverse Proxy is done using this container: https://hub.docker.com/r/linuxserver/letsencrypt/

What I'd like to do is have a second dynamic dns domain service access home-assistant on a different url, basically ..com

Anyone know if this is possible somehow?

I don’t know specifically through Letsencrypt but I’m sure it would be possible.

I run a DynDNS domain and DuckDNS one alongside each other, but just for remote access in case one doesn’t work so it’s a straight forward IP forward.

I would imagine you just specify a secondary configuration in Letsencrypt.

 

[xrapidx]

You want 2 different DNS names to point to the same public IP?
Don't see that working.

It currently works - the problem is the SSL certificate - and the second one goes to the upper level domain of the first one.

Going to keep fiddling with the letsencrypt docker image.

 

[GoneWithTheWindows]

It currently works - the problem is the SSL certificate - and the second one goes to the upper level domain of the first one.

Going to keep fiddling with the letsencrypt docker image.

Yea you are too quick, I gave it a second thought and deleted my post.
I need more coffee haha.

 

[irBosOtter]

You can point a million dns names to the same IP, but your setup makes it difficult with that docker and its limitations.
I would can the docker crap and just publish it directly with the router/firewall, not going through that reverse proxy setup.

 

[Johnatan56]

You running an Nginx proxy? Just make both domains there point to the same docker instance.

You can point a million dns names to the same IP, but your setup makes it difficult with that docker and its limitations.
I would can the docker crap and just publish it directly with the router/firewall, not going through that reverse proxy setup.

Just no.

 

[xrapidx]

You running an Nginx proxy? Just make both domains there point to the same docker instance.



Just no.

Yeh, the letsencrypt image includes nginx. just trying to figure out how to do what you just said. Letsencrypt allows you to use a wildcard for subdomains (which I need), but only with duckdns.

 

[DrJohnZoidberg]

As you're already using Docker, I'd recommend Traefik to handle proxying all your services. It handles all your LetsEncrypt certificates automatically too.

Here is an excellent guide that got me set up: https://www.smarthomebeginner.com/traefik-reverse-proxy-tutorial-for-docker/

Note: I'd recommend sticking with version 1 as the guide suggests.

If you don't need external access then you can just create a local only domain and use subdomains for everything (e.g. webmin.mydomain.local, cockpit.mydomain.local).

If you need access from the outside (I wouldn't really recommend this unless you really need it) then just get yourself a cheap domain name, and point your subdomains to a CNAME of your dynamic DNS host.

 

[xrapidx]

I do need mainly HA exposed to the internet. (and then anything it references in the code).

I think what I'm going to do is run two instances of the letsencrupt container.
1.) One for all subdomains, wildcarded with duckdns, e.g. service.<domain>.duckdns.org
2.) One for the other ddns domain, e.g <domain>.otherddns.com (which is home-asssistant)