Dyn DNS: Check IP detects single IP for multi-WAN
-
Hi,
Dyn DNS in a multi-WAN setup "suddenly" stopped working for me:
This is a pfSense CE HA cluster with one Internet access via PPPoE and one via a NAT router (4G). It has two DDNS clients configured for different Route53 host names, one on each interface. Since recently, both DDNS clients update to the PPPoE WAN IP only, i.e. the Check IP Service is detecting the PPPoE IP, despite it is set to monitor the interface to the 4G router.
Due to limited traffic volume, the 4G router should not be used for failover of the default route but only a VPN connection. Therefore, the PPPoE access was initially set as the default gateway. Then I moved PPPoE and the cluster sync interface into a GW group, to provide Internet access to the secondary cluster unit.
However, as far as I remember, DDNS was still working then. Since this smelled like a routing issue, I also changed it back and forth, tried other tricks (automatic default GW selection, different GW monitoring settings, adding GW groups for each interface only and monitor them in the DDNS configuration instead of the interfaces, adding unnecessary NAT to the 4G interface...).
After manual tests with "curl --interface", which also does not stick to the 4G interface, I suspect it can only be the curl version. I updated it at some point by "pkg-static upgrade". The units are on curl version 8.6.0, whereas another current pfSense CE has 8.4.0 (but no multi-WAN to test).
Can anybody confirm this observation or has another idea, please?
Thanks,
M