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
Marc, thank you so much for your work...I have what I believe is a little bit of a rare problem...I think I need to know what port/service the updater uses...I am using a dual wan load balancing router. I have all my HTTP traffic going though my cable connection (WAN1) and this is the ip I need to get to OpenDNS. However, the updater sends (WAN 2) ip address. If I add the service and protocol binding in my router I can tell it which WAN to use. Thanks.
Posted on
The updater is using HTTP (80), HTTPS (443) and DNS (53). You can check if all 3 connections use the same WAN IP by right-clicking the systray icon and launching the Diagnose option.