Login

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.


Issue created on

anonymous-43745098

Posted on

C-Myers wrote:

Since Mar 14 this has stopped working. I uninstalled and reinstalled and it sent one update and then stopped again. No matter what I change it never updates again.


mback2k

Posted on

Marc wrote:

Due to the guidelines of most DNS APIs the program only updates if the IP has changed since the last update. But you are right, I should make it update if you change some major settings. I will fix this soon.


anonymous-43912028

Posted on

C-Myers wrote:

Great,

It seemed like it wasn't working. The old version used to show that it updated at the scheduled time. Now it doesn't show that it has checked the IP to see if is the same. Just a verification in the log that it is still looking for a new IP. It worried me because DNS-O-Matic only showed an update from long ago.

I'll re-install and let it be.


mback2k

Posted on

Marc wrote:

Even the old version did not update if the IP did not change, but it did an update if the settings were altered or forced timeout happened. The forced timeout was an OpenDNS idea and it was randomly set between 6 and 12 hours if I recall correctly. I did remove this from the application to follow the general guidelines. But I will make the Updater update upon changed settings as soon as I get back to my dev machine.