Static route to update my DDNS - what am I doing wrong?

I have been trying to setup my NAS so that it is permanently connected to VPN, this is working over OpenVPN configuration from PIA and I can confirm when I use qbittorrent docker that the VPN address is being used, in this way I can use qbittorrent over my LAN instead of my client PC.

However I also have things like Plex, Emby and other services that I would like to connect to externally, for this purpose I setup DDNS, which was working fine so long as I was not connected to the VPN adapter. I found this tutorial to do some routing so that the external DDNS updated to my ISP IP, but it is not working. I sent a support ticket to ChangeIP.com and they told me they only use one IP to update the DDNS, which I added to a static route.

When I press update with the above configuration, the VPN IP is getting used:

Other notes: I wanted to use tcpdump to confirm the IP addresses being used to update ddns.info (ChangeIP.com) but the CPhub.net package source for Synology apps no longer works, so I couldn't install that. If we assume that ChangeIP.com really does only use that IP for checking DDNS updates then it should work.

When I go to Router Configuration it says "Your gateway settings is invalid" why? The service order is VPN > LAN (IP address of my ISP router) and enable multiple gateways is checked (enabled).

The NAS has a static LAN IP address.

Out of curiosity is anything else on the NAS required to be behind the VPN?

If not it might be better to keep things simple and use a qBittorrent Docker with VPN support built in. Binhex produce a popular Docker that even has a PIA configuration example: https://hub.docker.com/r/binhex/arch-qbittorrentvpn/

On 11/04/2023 at 10:28, InsaneNutter said:

Out of curiosity is anything else on the NAS required to be behind the VPN?

If not it might be better to keep things simple and use a qBittorrent Docker with VPN support built in. Binhex produce a popular Docker that even has a PIA configuration example: https://hub.docker.com/r/binhex/arch-qbittorrentvpn/

No, just the qbittorrent, so I will have a look at that, thanks!

Paging @BudManI would really like this option  

What option.. Multiple neworks on your interface 2.5g? Both?

Oh my bad thought this was a different thread.. let me look what your asking.

I am traveling an look via a remote connection to my desktop via chromebook so not all that easy to make out but its a bit difficult... I get back from travel on tuesday - so try and take a look at this thread on wed..  But I wouldn't do it this way, I would route traffic at my router not on my nas..  So I would set traffic for my qtorrent out vpn at my router since it would be using different IP then my normal nas.. And your dns settings are not ging to work like you want, you have no control if would use your local or public dns - going to be impossilbe to resolve stuff on google that ar elocal resources .

I ended up doing a Gluetun & Qbittorrent Docker container so this is no longer an issue.  

But to clarify, I wanted a permanent solution to keep my ever changing ISP IP updated for my ddns.