I'm using split horizon dns for my ddns domain. Because of this, the systemd service might cache the wrong ip address for the upstream server. If I'm on wifi, my ddns domain ip.me.link might link to 192.168.1.1, but outside my network, it might resolve to the external ip, like 80.160.45.13.
The systemd service does not re-resolve the ip when the network changes, so it might cache the local ip, and then the connection fails silently if you transition to another network. Instead, the systemd service should probably restart on network changes.
I'm using split horizon dns for my ddns domain. Because of this, the systemd service might cache the wrong ip address for the upstream server. If I'm on wifi, my ddns domain
ip.me.linkmight link to 192.168.1.1, but outside my network, it might resolve to the external ip, like80.160.45.13.The systemd service does not re-resolve the ip when the network changes, so it might cache the local ip, and then the connection fails silently if you transition to another network. Instead, the systemd service should probably restart on network changes.