Dynamic DNS Updater Client

nezmin2 · ‎10-27-2017

Hey Guys,

I recently reinstalled my Windows 10 Operating System and reinstalled the Dynamic DNS Updater client. I thought that everything was working fine until my wife's uncle showed up and showed me his tablet with porn running on it. After making sure that he was using my network, I started testing my OpenDNS setup. What I noticed is that the dynamic IP updater client wasn't running. I downloaded the latest version, reinstalled, and noticed that it shuts down almost immediately after launching. I went into the firewall and deleted all instances of the client and then reinstalled the app, however, it shut down immediately again. I am very perplexed. Is anyone else having this issue? If so, is there a fix? If not, could someone look into this for me and help me fix this? I have 5 kids plus their friends using my network and I need it to be safe for them.

Thanks...

rotblitz · ‎10-27-2017

Please note, the Updater works only if the computer is running and if the (admin) user who has installed it is actually logged in on this computer. If not all of these conditions are met, the Updater does not and cannot do its job.

There's another updater which runs as Windows service in the background and which does not require a user being logged on. You may try with this: https://updater.marc-hoersken.de/

And last but not least, it is ideal if you can run an update client on a device which is always switched on, like a router, NAS, DVR, IP camera, etc. These built-in DDNS update clients must be able to support one of OpenDNS, DNS-O-Matic, or "user defined / custom".

nezmin2 · ‎10-27-2017

The client is running on my PC which is always on and I am the admin on. My pc is also directly connected to the router where all other devices are run wireless.

rotblitz · ‎10-28-2017

I see, you insist in using this Updater.

"it shuts down almost immediately after launching."

What do the Windows event logs report about this symptom? I expect to see related entries there.
What does "%APPDATA%\OpenDNS Updater\log.txt" tell you?
Did you try to right-click the OpenDNSUpdater.exe to start it in elevated mode? Does it run and work then?

"Is anyone else having this issue?"

Apparently not. Did you consider to raise a support ticket with OpenDNS?

"could someone look into this for me"

Sure, if I can access your PC remotely, I could be looking into this, no problem.

"My pc is also directly connected to the router where all other devices are run wireless."

Sure, what else. It would be hard to connect it otherwise and still have LAN and internet connectivity.

nezmin2 · ‎10-28-2017

"I see, you insist in using this Updater." - This is the updater recommended by OpenDNS, however, I am now testing the one that you have suggested.

"What do the Windows event logs report about this symptom? I expect to see related entries there.
What does "%APPDATA%\OpenDNS Updater\log.txt" tell you?" -

sent ip update for user 'Nezmin2@gmail.com', response: 'nohost' url: /nic/update?token=0FF2189348EEF62147B136BC19CC440B&v=2&hostname=MXHome host: updates.opendns.com
Adding typo exceptions: natnow.rr.com,MAXGAMER,MXHOME

"Did you try to right-click the OpenDNSUpdater.exe to start it in elevated mode? Does it run and work then?" - Tried and No

"Did you consider to raise a support ticket with OpenDNS?" - Best practice is to search the forums, ask the community, and then submit a support ticket, which I was following.

"Sure, if I can access your PC remotely, I could be looking into this, no problem." - Uh, not gonna happen.

"Sure, what else. It would be hard to connect it otherwise and still have LAN and internet connectivity." - Just plain rude!

rotblitz · ‎10-29-2017

"This is the updater recommended by OpenDNS"

No, they do not recommend it, they just provide it. That's a big difference.
The recommendations are here: https://support.opendns.com/hc/en-us/articles/227988607
or here: https://support.opendns.com/hc/en-us/articles/227987767

"I am now testing the one that you have suggested."

The following advices are valid also for Marc's Updater.

You forgot to say whether or not the Windows event logs (eventvwr.exe) revealed anything related to the assumed program crashes.

"response: 'nohost'"

This is a culprit and not the expected response "good <IP address>"
as of https://support.opendns.com/hc/en-us/articles/227986527
Visit https://dashboard.opendns.com/settings/ to give your network a name which is called LABEL. Also ensure that you have dynamic IP address updates enabled for this network. Then configure the Updater to use this label as hostname, from the list as of https://support.opendns.com/hc/en-us/articles/227987807

"Uh, not gonna happen."

Well, you asked for exactly this. ("could someone look into this for me and help me fix this?")
And this is technically possible and often used. I'm not going to drive over to you to do it on-site.

"Just plain rude!"

No, just plain facts. Without direct connection to your router, be it wireless or wired, you'll have a hard time to go to the internet. Believe me!