DuckDNS Not Updating IP

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):

[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.

Zitat von gderf

What result do you get when you run the following command on the machine that has the problem?

dig domainame.duckdns.org

On the machine not working:

; <<>> DiG 9.10.3-P4-Debian <<>> domainame.duckdns.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10693
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;domainame.duckdns.org.         IN      A

;; AUTHORITY SECTION:
duckdns.org.            600     IN      SOA     ns5.duckdns.org. hostmaster.duckdns.org. 2021061901 6000 120 2419200 600

;; Query time: 35 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Jul 08 14:45:08 ADT 2021
;; MSG SIZE  rcvd: 101

On the machine that is working:

; <<>> DiG 9.10.3-P4-Debian <<>> domainame.duckdns.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53171
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;domainame.duckdns.org.         IN      A

;; Query time: 0 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Jul 08 14:45:29 ADT 2021
;; MSG SIZE  rcvd: 50

Zitat von gderf

Where is the ;; ANSWER SECTION:

I don't know. I wondered about that too. That is the working machine too.

Zitat von gderf

Code

curl: (6) Could not resolve host: www.duckdns.org

This would imply you have no working DNS on this machine. Try resolving some hosts on the CLI and see.

What do you mean "try resolving some hosts"? What do I type in?

Zitat von gderf

ping http://www.aol.com

ping cnn.com

If you get: Name or service not known then you have no working DNS.

root@HC2:~# ping google.com
PING google.com (172.217.11.14) 56(84) bytes of data.
64 bytes from lga25s60-in-f14.1e100.net (172.217.11.14): icmp_seq=1 ttl=117 time=20.4 ms
64 bytes from lga25s60-in-f14.1e100.net (172.217.11.14): icmp_seq=2 ttl=117 time=20.7 ms
64 bytes from lga25s60-in-f14.1e100.net (172.217.11.14): icmp_seq=3 ttl=117 time=20.8 ms
64 bytes from lga25s60-in-f14.1e100.net (172.217.11.14): icmp_seq=4 ttl=117 time=20.7 ms

Seems to ping just fine...

Zitat von gderf

Did you use your duckdns domain name or did you put domainame in the command?

Oh hahaha. I literally put "domainame." I was thinking it was a special command. LOL. Ok, here are the results, but with my actual domain name (edited out to be "domainame," and the IP address showing is edited to be "12.3.456.7" but the original was the old IP):

; <<>> DiG 9.10.3-P4-Debian <<>> domainame.duckdns.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16144
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;domainame.duckdns.org.              IN      A

;; ANSWER SECTION:
domainame.duckdns.org.       60      IN      A       12.3.456.7

;; Query time: 36 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Jul 08 16:08:14 ADT 2021
;; MSG SIZE  rcvd: 61

And the working machine (edited to be "domainame2" and IP address is correct but I edited to be 89.10.234.5):

; <<>> DiG 9.10.3-P4-Debian <<>> domainame2.duckdns.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63579
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;domainame2.duckdns.org.  IN      A

;; ANSWER SECTION:
domainame2.duckdns.org. 60 IN     A       89.10.234.5

;; Query time: 34 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Jul 08 16:09:14 ADT 2021
;; MSG SIZE  rcvd: 73

Zitat von gderf

All I can say is that the duckdns client instance is not working on that machine for some reason. Try deleting the container and build it again.

I already tried that. It was the first thing I did. So just now, I deleted everything and downloaded an old version of duckdns docker (it's from linuxserver). I used the tag arm32v7-44472b80-ls38. I tried to find the same one that is on the working machine, but I can't find it by its tag. So I used command line and tried to download by digest:

docker pull sha256:725dedce8fb60cb5bf9bc0262bc24129d717457baf3bbd4a12b4fb390d7f6dc7

It downloads it, but then on the docker GUI, it doesn't show the repository name or tag, and I can't run an image with it. So I don't think I'm doing it right. So anyways, I used the tag arm32v7-44472b80-ls38 instead (not the one I have on the working machine), and now I get this error in the logs (with my duckdns token for "token-number-token-number-token":

[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
/app/duck.conf: line 1: token-number-token-number-token: command not found
Something went wrong, please check your settings  Thu Jul 8 16:30:38 ADT 2021
[cont-init.d] 40-config: 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.

If you could help me get the same image as what's on the working machine, perhaps it will work for the non-working machine.

Zitat von gderf

Look here for the image you want:

https://hub.docker.com/r/linux…e=1&ordering=last_updated

If you find it you can copy the pull command on the right side and take what you need of it.

That's the problem I'm having. I can't find it. I tried ctrl+f on all 16 pages looking for part of the digest (725ded), but it's nowhere to be found. I need the tag for that specific digest. But I can't find the tag.

Okay, I have it working. I ended up choosing the tag arm32v7-version-4c2a0989 and it worked fine. For some reason, using the latest tag won't work for me. I have armv7 (Odroid HC2), but I'm not sure how to specify the digest with the latest tag. I don't really understand how the docker pulls work, and whether it detects my system and pulls the linux/arm/v7 digest.

Zitat von gderf

Another thing to consider if it's possible is to run a duckdns updater on your router. I do.

Yes, I do that as well. But I have a separate server name for sftp transfer so that the camera/sound guy at my church can transfer videos to the church server that I host at my house, and this keeps things neat and tidy in case I move the server to another location.