(Using the V2.2f build.)
For the past few hours, I've been seeing a very strange bug that seems to have sprung up totally out of the blue (that is, I wasn't even touching the PC), relating to updating the DynDNS IP. HFS began telling me it successfully updated my DDNS (at dyndns.org) with my alleged IP of 216.39.81.75, which is obviously not mine but the IP belonging and resolving to mywanip.com, one of the external IP checks used by HFS. This now happens every time HFS checks mywanip.com - a minute later, when HFS checks some other service, it corrects the DDNS entry back to my actual IP.
Log example, stripped of my actual IP (xx.xx.xx.xx):
2009-03-25 00:48:47 DNS update requested for 216.39.81.75: successful
2009-03-25 00:49:48 DNS update requested for xx.xx.xx.xx: successful
2009-03-25 00:50:49 DNS update requested for 216.39.81.75: successful
2009-03-25 00:51:50 DNS update requested for xx.xx.xx.xx: successful
2009-03-25 00:54:52 DNS update requested for 216.39.81.75: successful
25.03.2009 00:55:53 DNS update requested for xx.xx.xx.xx: successful
25.03.2009 00:58:55 DNS update requested for 216.39.81.75: successful
25.03.2009 00:59:56 DNS update requested for xx.xx.xx.xx: successful
25.03.2009 01:02:58 DNS update requested for 216.39.81.75: successful
25.03.2009 01:03:59 DNS update requested for xx.xx.xx.xx: successful
I don't know what's causing this, whether it's something new in the HTML that mywanip.com returns that's making HFS misinterpret and come up with this bug, or maybe a memory leak in HFS that lets it misuse the mywanip output. In any case it's not good. I've restarted HFS to see if that clears the error, no success. For now I've put mywanip.com into my hosts file with an entry pointing to localhost, so that HFS can't access mywanip at all.
