Update: A new beta version of the 1.5 series has again finally been released. The new DNS service providers all-inkl.com and inwx.com are supported and some code refactoring to support custom DNS and IP service providers has been performed. My plan is to have custom provider support and multiple account support for a 2.0 release this year.
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.
since 9 february 2019 I can't update with OpenDns service.
I receive this error:
"Upstream connect error or disconnected/reset before headers" (see attachment)
How can I resolve?
Thanks a lot
Since a week or two Marcs Updater isn't working any more on either Win7 x64 and Win 10.
Doesn't update at all with DynDNS... Very strange... Is this due to a Windows update? :-(
hi, ist it somehow possible to edit the serviceprovider? some kind of conf/xml to edit would be great.
my provider(all-inkl.com) offers ddns, but its not listed in the programm, or is there a way i could add on DDNS-Provider?
tnx & happy times
Hi Marc! Can you explain how the filter tabs work? I am hoping to have the updater ignore VPN connections if possible. Thanks!
Help Help Help !
Habe eine echt verzwickte Frage bei Problemlösung werde ich gerne eine grosszügige Donation machen :-))
Mein Netzwerk zuhause ist an einen DSL Router angeschlosen. Jetzt möchte ich zusätzlich noch einen LTE-Router einbinden, der kann aber kein Internet sondern NUR ausschliesslich VPN (alles ausser PPTP und IPSec wird beim Provider verworfen). Damin komme ich dann von aussen in mein Netzwerk und habe einen viel schnelleren Upload als mit der DSL-Verbindung.
Antwort an: falamoet-online.de
Danke + Cheers,
Can you suggest why I can't update my IP at OpenDNS.com? I have had 220.127.116.114 installed on a WHS 2011 unit for quite a while and it was working fine. I was recently logged into the server desktop and I saw it wasn't updating. OpenDNS.com had an out-dated IP address for my network. The updater showed a message "The username and password pair do not match a real user. Please check your settings to continue." I have checked and double checked the credentials - which work fine when I log in at OpenDNS.com. I have the correct network name in the Hostname field. I have tried using 18.104.22.1680. I have tried installing the updater on another WHS 2011 system as well as two different Windows 10 systems. Everything looks normal and it used to work but it doesn't now. I see only 'badauth' under IP Updates (although there is a green check mark at the front of each line.
A strange thing is that I started Wireshark and I see the updater communicating with updates.dnsomatic.com first before talking to updates.opendns.com. It's encrypted, of course, so I couldn't see the data.
If I install OpenDNS Updater 2.2.1, I can run it with the same credentials and it updates properly. Thanks for any assistance.
We have a failover in place on our router and recently we've been having issues with marcs updater constantly changing the IP back and forth between our primary IP and our secondary failover IP. We use marcs updater because we have a ton of problems with sonicwall's DDNS updater and I'm hoping this doesn't mean we will need to switch back. Any ideas? I was in our server earlier and Marcs Updater changed the IP about 5 times in the course of a minute.
Is possible to add Internet.bs DDNS service ( http://www.internetbs.net ) ?
it is possible to use wget to update the ip. Here is a sample url:
Note both URLs i gave you are using https but you can also use http however, for security reasons, we
recommend using https.
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:
I'm going to use this application with openDNS service to block urls. Actually I don't understand how WiFi filtering is working (maybe because English are not my language). Filtering a ssid means that only when connected to it, the service will run? Or the excluded ssids won't be updated?
Is there a way to recognize the wired LAN which is connected, in order to be managed like ssids?