The Feature request:
Set the ip addresses per domain:
The current duckdns-addon configuration.
lets_encrypt:
accept_terms: true
certfile: fullchain.pem
keyfile: privkey.pem
token: '!secret DuckDNS-Token'
domains:
- homeassistant.duckdns.org
- homeassistant-local.duckdns.org
aliases: []
seconds: 300
The requested duckdns-addon configuration:
lets_encrypt:
accept_terms: true
certfile: fullchain.pem
keyfile: privkey.pem
token: '!secret DuckDNS-Token'
domains:
- homeassistant.duckdns.org
- homeassistant-local.duckdns.org
Ip4v: 192.168.1.2
aliases: []
seconds: 300
Context:
My family got interested in Home Assistant. But they still have the isp router.
Which means that it isn’t possible to set a DNS server, nor the option to change the DCHP server.
To got an encrypted connection locally and remotely I created two duckdns addresses.
Homeassistant.duckdns.org
Homeassistant-local.duckdns.org
Now the Addon sets both urls to the external IP address. The solution I’m using now is to enable the addon a few minutes a day with an automation. And then set the local url with an rest command.
Enabling a feature to set the ip address per domain would make this a lot simpler.
It is fully supported in the app. Which has an option to use two urls.
And unlike the ‘NGINX Home Assistant SSL proxy’, the local connection is encrypted.