Comments

5 comments

  • Avatar
    rotblitz

    What hostname did you specify in your update client sending the requests to DNS-O-Matic?  Try with all.dnsomatic.com then if you didn't use this anyway.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Also, regarding your picture, the last IP address change was on Mar 10 7:09am, but you only added the Tunnelbroker service on Mar 10 5:08pm.  So, why should there be an update if the IP address didn't change at all?  There is none!  You must initiate the first update manually, or you must wait until an IP address change occurs which is reported by your local update client to DNS-O-Matic.

    Nothing in the world happens automagically - never ever...

    0
    Comment actions Permalink
  • Avatar
    warfab

    The hostname I tried is "all.dnsomatic.com". 

    Maybe the latest screenshot will help explain my dilemma ... I didn't change anything since the first screenshot.




    DNSOMATIC_02.jpg
    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Yes, open a support ticket.  Staff must look into your account.

    0
    Comment actions Permalink
  • Avatar
    Alexander Harrison

    It looks like you've added tunnelbroker as a new service (but have kept the same updating mechanism). Has your IP updated to the other services since you first added tunnelbroker? If not, Your IP would have to change before the first update is pushed and the configuration only not working for Tunnelbroker would indicate the area for investigation is the tunnelbroker authentication for updates. Once your other services IPs have updated, confirm if Tunnelbroker also updates with the update. 

    0
    Comment actions Permalink

Please sign in to leave a comment.