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
Doug Valkenaar wrote:
When I first start up the program (or reboot the system) it'll send an update to OpenDNS but then it stops sending updates. For example, today my IP changed at 3am and it's now 11:45pm and not updated. I restarted the Updater service and my IP was immediately updated on OpenDNS.
I'm running WinXP.
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.
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.
Posted on
www wrote:
Is there a way to disable the "you are not using OpenDNS nameservers" notification?
Posted on
tadej wrote:
Nothing really imporant though, but I just want to report a minor problem with Marcs Updater when it's used (that is, the service component/process) in cooperation with PsService program (basically it does same as Windows Net program) from Sysinternals. And with problem I mean that it doesn't (at least always) work as expected/it should.
So while pausing/resuming the service (almost always) works normally, restarting the service for example exists the process rather than restarting it.
Posted on
tadej wrote:
Hey Marc, I see that I (tadej from OpenDNS Forums) am the first poster here...
I am just reporting that today when I launched Marc's Updater I got a notice that a new version is available and it was downloaded "internally" (by some "update.exe" process launched in the TEMP directory, I assume started by "Marcs Updater.exe") and then on installation of this new version I the following error windows popped-up:
/EDIT: Oh and yes, here is all the code from this window:
Invalid memory access Code = -1073741819 Line = 277 File = Network.pbi OSV = 0x3C EIP = 0xFFFFFFFFDCDC43D0 ETP = 0xFFFFFFFFDCDC43D0 EAX = 0x14C0048 EBX = 0x0 ECX = 0x77F58EC1 EDX = 0x0 EBP = 0xFFFFFFFFDEDE43D0 ESI = 0x0 EDI = 0x0 ESP = 0x12BFFA4
And the same happened when I downloaded the "Marcs Updater.exe" installer from this link here on this forum.
Best regards, Tadej