I have two separate NAS servers, each running their own instance of OMV and docker, each with DuckDNS set up. I just changed ISP's, and on one server, DuckDNS updated fine, and on the other, DuckDNS still has my old IP address. I don't understand why. Any idea on where to start with troubleshooting? I already nuked it by deleting the DuckDNS docker and image, and redownloading everything and setting it up again. It still won't show my new IP address.
Here is what the log shows (on the server where DuckDNS isn't working right):
Code
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 40-config: executing...
Retrieving subdomain and token from the environment variables
log will be output to docker log
curl: (6) Could not resolve host: www.duckdns.org
Something went wrong, please check your settings Thu Feb 4 11:06:40 AST 138072
The response returned was:
[cont-init.d] 40-config: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Alles anzeigen