DynDNS wrong external IP (permanent switch between WAN IP and VPN-tunnel IP)

[Matzke]

Dear All,

I'm using os-ddclient 1.13_2 on OPNSense 23.1.9.

I have 2 WAN interfaces and one VPN-tunnel to an VPN-Provider.

WAN A is connectet to a Telekom DSL Line (with speedport router in between)
WAN B is connected to a EURODOCSIS Modem (actual switched off)
NordVPN tunnel is established (used for example for Guest WLAN via Firewall rules as a different gateway)

os-ddclient now alternates the public DNS between WAN A (which is correct) and NordVPN external IP.

I don't know why it detects this IP and submits this to the DynDNS provider. In os-ddclient I setup "interface to monitor" -> my Interface which is directly connected to Telekom Speedport Router.
Check-ip-method is ipify-ip4

Backend: OPNSense (dd-client won't work with desec / dedyn.io provider -> there it deletes my A-Record instead of updating it - but also backend dd-client switches between both IP adresses).

It permanently switches between both IP addresses.

[Matzke]

Any ideas why it doesn't use the "interface to monitor" to determine the right external IP address or how I can analyze this problem?

Normally it shouldn't use the vpn device for determining external ip - in my setup it seems to switch between both interfaces in every cycle (300 sec).

Thanks a lot

[chemlud]

...have you tried other methods for IP check? "Interface" and/or some others?

[Matzke]

yes, former methods were noip and also interface (but this reports my private IP of WAN interface).

[Matzke]

Dear all,

using "check-ip-method" - "Interface (ipv4)" seems to work stable now.

But it's strange - in settings the fields "Current IP" and "Updated" are wrong therefor I didn't realized that in background the right IPs are updated (after a lot of trial and error with the settings).

The strange behavior seems to be stable - "Current IP" and "Updated" show rarely the right values.

(But to keep clear - the problem of this post was real - I can see the history in one of my dyndns accounts which shows the switch of both IPs (VPN and real IP) - but I can't retrace which setting was used in past)

[Matzke]

just a followup

using ddclient and check ip method "Interface" I got my internal IP reported to dyndns (10.1.1.1 for example) - using the same with opnsense backend it resolves my external IP.

I don't know why - I doesn't changed the config but my problem is back (when writing my last post it seemed to work properly and I never looked again in the logfiles - but yesterday I noticed that my problem are back again. At first I thought only one dyndns server is affected (the server with check ip method NOT interface(ipv4)). Now I checked the logs and can see it is also with check-ip-method "interface" - so I think it is independend from this setting.

I don't know where to look for problems - logfiles in opnsense are empty when using opnsense backend.

2023-06-25 23:19:22   217.85.x.x   OPNsense-dyndns
2023-06-25 23:14:19   176.223.y.y   OPNsense-dyndns
2023-06-25 23:04:15   217.85.x.x   OPNsense-dyndns
2023-06-25 22:59:13   176.223.y.y   OPNsense-dyndns
2023-06-25 22:54:11   217.85.x.x   OPNsense-dyndns
2023-06-25 22:49:09   176.223.y.y   OPNsense-dyndns
2023-06-25 22:44:07   217.85.x.x   OPNsense-dyndns
2023-06-25 22:28:53   176.223.y.y   OPNsense-dyndns
2023-06-25 22:23:50   217.85.x.x   OPNsense-dyndns
2023-06-25 22:13:45   176.223.y.y   OPNsense-dyndns
2023-06-25 22:08:43   217.85.x.x   OPNsense-dyndns
2023-06-25 21:48:34   176.223.y.y   OPNsense-dyndns
2023-06-25 21:43:31   217.85.x.x   OPNsense-dyndns
2023-06-25 20:58:13   176.223.y.y   OPNsense-dyndns
2023-06-25 20:53:10   217.85.x.x   OPNsense-dyndns
2023-06-25 19:57:43   176.223.y.y   OPNsense-dyndns
2023-06-25 19:47:26   217.85.x.x   OPNsense-dyndns
2023-06-25 19:42:15   176.223.y.y   OPNsense-dyndns
2023-06-25 19:37:13   217.85.x.x   OPNsense-dyndns
2023-06-25 18:56:18   176.223.y.y   OPNsense-dyndns
2023-06-25 18:51:13   217.85.x.x   OPNsense-dyndns
2023-06-25 18:35:56   176.223.y.y   OPNsense-dyndns
2023-06-25 18:25:42   217.85.x.x   OPNsense-dyndns
2023-06-25 18:05:10   176.223.y.y   OPNsense-dyndns
2023-06-25 17:59:58   217.85.x.x   OPNsense-dyndns
2023-06-25 17:54:47   176.223.y.y   OPNsense-dyndns
2023-06-25 17:49:41   217.85.x.x   OPNsense-dyndns
2023-06-25 17:39:18   176.223.y.y   OPNsense-dyndns
2023-06-25 17:28:58   217.85.x.x   OPNsense-dyndns
2023-06-25 17:23:55   176.223.y.y   OPNsense-dyndns
2023-06-25 17:18:52   217.85.x.x   OPNsense-dyndns
2023-06-25 17:13:47   176.223.y.y   OPNsense-dyndns
2023-06-25 17:08:42   217.85.x.x   OPNsense-dyndns
2023-06-25 16:58:27   176.223.y.y   OPNsense-dyndns
2023-06-25 16:38:11   217.85.x.x   OPNsense-dyndns
2023-06-25 16:32:59   176.223.y.y   OPNsense-dyndns
2023-06-25 16:22:46   217.85.x.x   OPNsense-dyndns
2023-06-25 16:12:31   176.223.y.y   OPNsense-dyndns
2023-06-25 16:07:20   217.85.x.x   OPNsense-dyndns
2023-06-25 16:02:08   176.223.y.y   OPNsense-dyndns
2023-06-25 15:46:37   217.85.x.x   OPNsense-dyndns
2023-06-25 15:41:35   176.223.y.y   OPNsense-dyndns
2023-06-25 15:36:24   217.85.x.x   OPNsense-dyndns
2023-06-25 15:31:13   176.223.y.y   OPNsense-dyndns
2023-06-25 15:26:02   217.85.x.x   OPNsense-dyndns
2023-06-25 15:20:59   176.223.y.y   OPNsense-dyndns
2023-06-25 15:10:53   217.85.x.x   OPNsense-dyndns
2023-06-25 15:00:40   176.223.y.y   OPNsense-dyndns
2023-06-25 14:55:36   217.85.x.x   OPNsense-dyndns
2023-06-25 14:40:28   176.223.y.y   OPNsense-dyndns
2023-06-25 14:35:16   217.85.x.x   OPNsense-dyndns
2023-06-25 14:30:05   176.223.y.y   OPNsense-dyndns
2023-06-25 14:24:54   217.85.x.x   OPNsense-dyndns
2023-06-25 14:19:50   176.223.y.y   OPNsense-dyndns

[Matzke]

DynDNS Problems back again after upgrade to 23.7

The Client seems to be completely broken because either it reports strange IPs (independend from choosen method it mostly reports IPs not belonging to my external IP) or it doesn't work at all (not updating anything).

I had to switch to the ddns updater integrated in my router - but normally everything should be done by my opnsense.

Both backends doesn't work (ddclient as well as opnsense).

[swojcik]

could this be why noip.com decides it's going to use my desktop client public VPN address as the IP it thinks is my WAN address?

Hopefully what I said makes sense. I'm pretty new to opnsense so I was just hoping it was a setting I biffed somewhere. It's pretty annoying any time one of my services that uses my dynamic DNS address stops working, I have to turn on OpenVPN to see if my public IP has changed (I have straight talk home Wi-Fi and it does more often than you would think) then login to noip and manually update my IP / Target