I upgraded my UTM to 9.501-5 around lunchtime today. Everything appeared to go fine, but later this afternoon I realized that I hadn't received any legitimate emails since that time - the only incoming mail was from spambots. I decided to check my DynDNS entries against my external IP address, in case my ISP had given ne a new IP after the update and reboot, and dure enough, I discovered that my DynDNS entries were wrong.
But they weren't just out-of-date, they were wrong - they had both been set to 192.168.100.2! Examination of the Host Update log at DynDNS showed that they had both been updated at exactly the time that the UTM came back up after rebooting:
| 2017-06-13 17:52:38 | ******.homeip.net ******.tzo.net |
192.168.100.2 | system=dyndns | ddclient/3.8.2 (using SSL) | good 192.168.100.2 good 192.168.100.2 |
And checking the System log on the UTM I see
/var/log/system.log:2017:06:13-12:47:37 astaro ddclient[6300]: WARNING: cannot connect to members.dyndns.org:443 socket: IO::Socket::SSL: getaddrinfo: Name or service not known IO::Socket::INET6 configuration failed
/var/log/system.log:2017:06:13-12:47:37 astaro ddclient[6300]: FAILED: updating ******.homeip.net,******.tzo.net: Could not connect to members.dyndns.org.
/var/log/system.log:2017:06:13-12:47:37 astaro ddclient[6300]: WARNING: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org'
/var/log/system.log:2017:06:13-12:52:37 astaro ddclient[6300]: WARNING: file /var/cache/ddclient/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''
/var/log/system.log:2017:06:13-12:52:37 astaro ddclient[6300]: WARNING: file /var/cache/ddclient/ddclient.cache, line 4: Invalid Value for keyword 'ip' = ''
/var/log/system.log:2017:06:13-12:52:38 astaro ddclient[6300]: SUCCESS: updating ******.homeip.net: good: IP address set to 192.168.100.2
/var/log/system.log:2017:06:13-12:52:38 astaro ddclient[6300]: SUCCESS: updating ******.tzo.net: good: IP address set to 192.168.100.2
I've manually set both entries via DynDNS's web interface, but I'm concerned that the DDNS client on the UTM will reset them back again at some point. I'm also puzzled where the hell it got the 192.168.100.2 address from, as that is not in any of my configured private networks.
This thread was automatically locked due to age.