Dynamic DNS NO-IP - Using incorrect WAN IP
I've setup NO-IP Dynamic DNS as per the user guide to use the WAN IP address however; NO-IP always seems to have the IP address of the WAN/LAN1 IP instead. It's the only Dynamic DNS record on the controller.
Looking at the logs, it seems like the correct WAN port is first used to bind the correct IP address to the domain as scheduled however; 2 minutes later another update is sent with the other WAN/LAN1 and incorrect IP address. Is this a bug?
WAN/LAN1: No-IP DDNS logining succeeded, username is ************. May 13, 2024 20:02:26
WAN/LAN1: No-IP DDNS registeration/update succeeded. 92.##.##.106 and *********.ddns.net are bound. May 13, 2024 20:02:26
WAN: No-IP DDNS logining succeeded, username is ************. May 13, 2024 20:00:13
WAN: No-IP DDNS registeration/update succeeded. 178.###.###.44 and *********.ddns.net are bound. May 13, 2024 20:00:13
WAN/LAN1: No-IP DDNS logining succeeded, username is ************ May 13, 2024 19:02:24
WAN/LAN1: No-IP DDNS registeration/update succeeded. 92.##.##.106 and *********.ddns.net are bound. May 13, 2024 19:02:24
WAN: No-IP DDNS logining succeeded, username is ************. May 13, 2024 19:00:12
WAN: No-IP DDNS registeration/update succeeded. 178.###.###.44 and *********.ddns.net are bound. May 13, 2024 19:00:12
WAN/LAN1: No-IP DDNS logining succeeded, username is ************ May 13, 2024 18:02:23
WAN/LAN1: No-IP DDNS registeration/update succeeded. 92.##.##.106 and *********.ddns.net are bound. May 13, 2024 18:02:23
WAN: No-IP DDNS logining succeeded, username is ************. May 13, 2024 18:00:11
WAN: No-IP DDNS registeration/update succeeded. 178.###.###.44 and *********.ddns.net are bound. May 13, 2024 18:00:11