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
I've finally found time to use this great app but I found a downside compared to the opendns updater:
It doesn't update when network is connected but only after the update interval. This means that certain actions that I'm trying to prevent won't be blocked at all because if dns resolving is already done, the addresses will be accessible.
Dns Update action for blocking should be done before the applications connect to the internet.
Are you going to make it updating at the time it is connected to a network?
Is there a command to update manually earlier than time interval? I'm thinking to create a scheduled task to do it for now and something like this:
Posted on
Actually, it should be updating once you are connected to a network. Which version are you using? Did you try the current beta version?
Posted on
No but I'm going to check it soon. I don't have the appropriate conditions now. I hope soon and I'll report back.