Update all DNS-O-Matic services from OpenDNS Updater client app

Comments

5 comments

  • Avatar
    mattwilson9090

    This is already supposed to happen. When the Updater sends an update to DNS-O-Matic, DNS-O-Matic then sends updates to all services configured on your DNS-O-Matic account. It's what happens for me, although for the last few years I've been sending updates from my router's firmware rather than running the Updater app.

    This is precisely what DNS-O-Matic is intended to do, handle the updates itself, rather than have a client communicate with each individual service.

  • Avatar
    cobalt-phoenix

    "The only change it should require is adjusting the "Host" in the outgoing request to be set to "all.dnsomatic.com"."

    Yes, do this!  Does anything prevent you from changing the hostname to all.dnsomatic.com?

  • Avatar
    justinsirois

    mattwilson9090 said: "It's what happens for me, although for the last few years I've been sending updates from my router's firmware rather than running the Updater app."

    When I use my router's firmware I can get it to update all services.  The reason that isn't an option for me is my ISP requires use of their router, and they only offer a handful of DDNS options.  The two I need are not on that list (OpenDNS and NameCheap).  I also have an OpenWRT variant router that does work well with DNSOMatic, but but since it sits behind the ISP's router, it receives an IP in the private 192.x.x.x space and attempts to send that out as the public address to DNSOMatic.

    cobalt-phoenix said: "Does anything prevent you from changing the hostname to all.dnsomatic.com?"

    If you are asking me, the official app doesn't allow you to change the hostname.  You log in with your OpenDNS account username and password and it sets the network behind the scenes.  If that was directed at the dev's, I agree :)

  • Avatar
    cobalt-phoenix

    I rarely used the OpenDNS Updater, so didn't recall that you can select only OpenDNS network label names from the drop-down list.

    No matter, I have a solution for you: https://updater.marc-hoersken.de/

    And I even have a second solution for you:

    "I also have an OpenWRT variant router that does work well with DNSOMatic, but but since it sits behind the ISP's router, it receives an IP in the private 192.x.x.x space and attempts to send that out as the public address to DNSOMatic."

    This argument doesn't count.  You can use the option ip_source 'web'  and  option ip_url http://myip.dnsomatic.com/  -  and you're done!
    https://wiki.openwrt.org/doc/uci/ddns

    Now you've got even two options.  It's your choice.

  • Avatar
    justinsirois

    Thanks!

    Marc's updater is the one I've been using since finding out the OpenDNS client wouldn't do what I needed. 

    Thank you for mentioning the router option.  That is the solution I really wanted from the get-go, but had given up on.  I made a mistake in saying my router's firmware was based off of OpenWRT, (it's actually ASUSWRT-Merlin which has it's roots in Tomato)  none-the-less your comment made me look into what was possible, and I now have it working and am glad to be rid of the client software updaters.

Please sign in to leave a comment.