Marcs Updater
There have been some reports about issues with the Updater not updating anymore. Please try the latest beta version and switch to another IP Check provider instead of the previous default dnsomatic.com. For some reason they are rate-limiting the number of requests to their service. The new IP Check provider selection allows you to choose another provider in such cases. You can test the functionality with the new "Test" panel.
If you want to add a custom provider to the unstable testing version, store a JSON file like the following under %PROGRAMDATA%\Marcs Updater\ServiceProviders\dyndns.json:
{
"name": "DynDNS.org (Test)",
"endpoint": "https://members.dyndns.org/nic/update",
"method": "GET",
"queryString": "hostname={HOSTNAME}&myip={MYIP}",
"dataPayload": "",
"defaults": {
"username": "test",
"password": "test",
"hostname": "test1.customtest.dyndns.org"
}
}Supported query and payload tags are {USERNAME}, {PASSWORD}, {HOSTNAME} and {MYIP}. Restart the background service and foreground application to apply any changes.
Posted on
Guest wrote:
Hello Marc, and seasons greetings. I wondered if there was anything I could do to help you get to the bottom of the issue with the wireless and network filtering not working for me?
Posted on
Guest wrote:
Hi Marc, any further thoughts on the wireless network filtering issue below? Are there more diagnostics that would help you determine why this function doesn't work for me?
Posted on
Guest wrote:
Here's an example of wireless network filtering not working. I notice that in the log and also in the Wireless Network tab, the current SSID shows empty. There are four entries in the allowed box. Even with an empty current network (which is incorrect), you should have found that "empty" != "somthing-else"
I am assuming the entries in the Wireless Network filtering page are the allowed ones, of course
1524 2011-11-22 18:35:34 INFO [Marcs Updater.pb:ThreadServiceWait:0570] Registry change triggered
092C 2011-11-22 18:35:34 INFO [Marcs Updater.pb:ThreadServiceMain:0606] Semaphore signaled, continuing service
1524 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceWait:0588] Closing wait handles
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:TestNetwork:0317] Testing network filter
1524 2011-11-22 18:35:34 DEBUG [Marcs Updater.pb:ThreadServiceWait:0593] Thread stopped
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:TestNetwork:0332] Wireless network filter active
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:TestNetwork:0334] Network =
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0608] No network filter prevented update, testing internet
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0610] Try number 0
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0620] Internet is connected, checking IP using HTTPS
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0623] Validate current IP = xx.xx.xx.xx
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0625] Reading previous results from registry
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0631] Resetting ForceUpdate flag
092C 2011-11-22 18:35:34 INFO [Marcs Updater.pb:ThreadServiceMain:0634] Current IP is valid, compare to previous
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0635] CurrentIP = xx.xx.xx.xx
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0636] PreviousIP = yy.yy.yy.yy
092C 2011-11-22 18:35:34 INFO [Marcs Updater.pb:ThreadServiceMain:0638] Current IP does not equal previous IP
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0651] OpenDNS limit = 180 > 9246
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0652] Week limit = 180 > 606422
092C 2011-11-22 18:35:34 INFO [Marcs Updater.pb:ThreadServiceMain:0663] Checking for forced update, IP change or time limit
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0664] ForceUpdate = 0
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0665] Changed = 1
092C 2011-11-22 18:35:34 TRACE [Marcs Updater.pb:ThreadServiceMain:0666] Limit = 0
092C 2011-11-22 18:35:34 INFO [Marcs Updater.pb:ThreadServiceMain:0668] Reading username from registry
092C 2011-11-22 18:35:34 INFO [Marcs Updater.pb:ThreadServiceMain:0671] Sending IP update to remote service
092C 2011-11-22 18:35:35 TRACE [Marcs Updater.pb:ThreadServiceMain:0680] Checking for empty result
092C 2011-11-22 18:35:35 INFO [Marcs Updater.pb:ThreadServiceMain:0682] Result is not empty, splitting into code and IP
092C 2011-11-22 18:35:35 INFO [Marcs Updater.pb:ThreadServiceMain:0699] Result = good
092C 2011-11-22 18:35:35 INFO [Marcs Updater.pb:ThreadServiceMain:0705] Setting next timer timeout to 8054 seconds
092C 2011-11-22 18:35:35 TRACE [Marcs Updater.pb:ThreadServiceMain:0724] Updating registry with latest result
092C 2011-11-22 18:35:35 TRACE [Marcs Updater.pb:ThreadServiceMain:0763] Checking for waiting thread
092C 2011-11-22 18:35:35 TRACE [Marcs Updater.pb:ThreadServiceMain:0770] Starting new waiting thread
092C 2011-11-22 18:35:35 TRACE [Marcs Updater.pb:ThreadServiceMain:0603] Service running, waiting for semaphore signal
1724 2011-11-22 18:35:35 DEBUG [Marcs Updater.pb:ThreadServiceWait:0559] Thread started
1724 2011-11-22 18:35:35 TRACE [Marcs Updater.pb:ThreadServiceWait:0561] Registry key exists, setting up registry and timer wait handles
1724 2011-11-22 18:35:35 TRACE [Marcs Updater.pb:ThreadServiceWait:0567] Waiting for handles
Posted on
Tom Hargraves wrote:
Hi Marc,
The balloon pop-ups are appearing every 120 minutes (the max), telling me that the IP address has been updated to exactly the same address as it was.
Is there any way get them to only pop-up when the IP address actually changes?
Thanks,
Tom.
Posted on
Michael Kendrick wrote:
I have a problem with the software. I NEVER turn my computer off, and am always active. My ISP never seems to change the IP (I've had the same IP for at least a year). The problem is that since I never turn off the computer and my IP never changes, DNS-o-Matic isn't being updated. Every month I get an e-mail stating my account's going to be closed.
Can you build something into the program that forces an update once a week regardless of whether or not the IP changed? I can't be the only one having this issue.
Posted on
Cmyers wrote:
I am finding an issue with my IP. It stays the same for many months so Marc's doesn't send an update. This is a problem with No-IP.org as it needs to get an update every 60 days. I would like it to always send an update to DNS-O-Matic at least once a week even if there is no new IP address.
I can do it by hand, but that isn't handy.
Posted on
Allen wrote:
Hi.
Since installing the updater, Zonealarm notifies me periodically that the updater is trying to open a port to allow incoming connections, (act as a server). I have disallowed this and the updater is still working. I am only updating OpenDNS. Why is the updater trying to act as a server?
Thanks.