UGREEN NAS + Porkbun DNS

[bryury]

Has anyone tried the ddns-updater with a NAS like UGREEN NAS?
I'm struggling to get this working for me.

For my DNS provider, I am using Porkbun. And have been following the instructions here:
Porkbun Instructions
Porkbun Github

My apps on my NAS are deployed via Docker compose. Ddns-updater provides a docker compose file. So the steps I am following are slightly different from the default steps that are provided. I tried to modify the steps here from a QNAP Setup Guide.

Workflow overview

• Create 'ddns-updater' directory in Docker share
• Inside the created directory, create 'app' and 'data' directories
• Create config.json and updates.json
• Generate keys on Porkbun
• Edit config.json (add Porkbun keys)
• Move config.json and updates.json to the 'data' directory (moved via ssh)
• Modify docker compose (volume, user)
• Check firewall ports
• Create container with docker compose file

Detailed Work

Directories
On my UGREEN NAS, I created the 'ddns-updater' directory in my Docker shared folder. Inside the created directory, I created 'app' and 'data' directories

Generate Keys on Porkbun
Enabled API Access
Created API key and Secret key required for the config.json later.

JSON Files
I modified my config.json to similar to below, below is just an example.

{
  "settings": [
    {
      "provider": "porkbun",
      "domain": "yourdomain.example",
      "api_key": pk1_5299b57125c8f3cdf347d2fe0e713311ee3a1e11f11a14942b26472593e35368",
      "secret_api_key": "sk1_7d119e3f656b00ae042980302e1425a04163c476efec1833q3cb0w54fc6f5022"
    },
    {
      "provider": "porkbun",
      "domain": "www.yourdomain.example",
      "api_key": "pk1_5299b57125c8f3cdf347d2fe0e713311ee3a1e11f11a14942b26472593e35368",
      "secret_api_key": "sk1_7d119e3f656b00ae042980302e1425a04163c476efec1833q3cb0w54fc6f5022"
    }
  ]
}

I left 'updates.json' as blank.
I moved both folders to my UGREEN NAS via ssh into the 'data' directory created earlier.

Docker Compose
Grabbed the official template from here.

Changed the volume information to match my path

volume:
 - /volume2/docker/ddns-updater:/updater/data

Changed my restart to

restart: unless-stopped

Firewall Port
I disabled the firewall on my NAS (testing purposes).
The NAS sits behind a router (Does a port need to be forwarded here?).

Container
Started the container

Result

I get no error when the container starts up.
However, when I go to Porkbun to check the DNS records, it does not point to my IP. Therefore, something did not work correctly.

Any insight or tips are greatly appreciated!

[riotinprogress]

@bryury, did you ever get this going? I'm about to attempt it myself.

[bryury]

Nope, never finished this.
My ISP at the time was kinda crappy. So now that I've moved, I may try my hand at it again. But may take some time before I do it.
Let me know how it goes for you.

Also, the DDNS ports likely need to be opened not only on the firewall of your NAS, but also at the router I think. Port Triggering may be necessary.