I have CasaOS/Ubuntu server running on a mini pc connected to my VPN router. My DuckDNS docker updates my DuckDNS to my VPN IP address. If there any way to make it update to my true IP address?
What would be the point of having a “DuckDNS docker” that returns something other than its public IP address?
If it’s connected through your VPN…its public address is your VPN.
If you don’t connect it through your VPN…then its public address is your public address.
When it is using the VPN address it occasionally is able to connect (I am not clear how this is even possible as the IP address is shared).
When I update DuckDNS with my true IP address it connects reliably until the DuckDNS docker updates the IP to the VPN address.
To me that would suggest that neither your VPN nor your DuckDNS docker are set up properly.
Why are you connecting your DuckDNS docker to your VPN instead of routing through your normal gateway? It quite literally does not belong there and cannot perform its function if it is connected to the VPN unless the VPN is misconfigured.
My server is connected to my VPN router. All traffic is behind VPN. I would like to allow DuckDNS to bypass VPN, but I am not sure how to do that without having everything on the server bypass VPN.
You should look into properly setting up a reverse proxy for your use case rather than a VPN if your intention is to use DuckDNS to access some or all of your self-hosted apps.
As the other poster has suggested, the fact that DuckDNS is routing through to your true IP address even though your VPN is active is a major red flag that something is not configured correctly and you are risking exposure of your internal network to who knows what.
It’s docker. You can just use e.g. a macvlan network to give it its own address on whatever network you choose. And then set your VPN and/or router appropriately.
If “everything” goes through your VPN the only way you will ever have it not return the VPN IP is if your VPN is leaking, which presumably defeats your entire purpose of routing everything through a VPN.
Thanks. Just to clarify… The DuckDNS docker container was not accessing my true IP address. I did resolve this by configuring my openwrt VPN router with the DDNS app for DuckDNS.