Package: ez-ipupdate Version: 3.0.11b8-8.1 I noticed this issue just today. I'm running ez-ipupdate with the free DynDNS service. I had originally had the machine running as e1.xyz.com, and had changed the config to e2.xyz.com, although the monitored IP address remained the same. I was surprised to find out that for a week or two now, the new address was never sent to dyndns. Apparently, ez-ipupdate read the interface IP from its cache, and determined nothing needed to be done, never realizing I had set an entirely different subdomain to be updated. To solve the issue I had to delete the cache file to force an update. Shouldn't the domain be cached as well, so as to detect changes in the domain like this?
-- Matt LaPlante -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
