Problems updating with all.dnsomatic.com as hostname

Follow

rickny

December 01, 2016 17:38

I started having an issue this morning where trying to update my account using all.dnsomatic.com as the hostname is not working to update all of my services.. I typically use this under pfSense, but even though the update shows successful, listing all of my hostnames on my account are showing my old address, with a last update time of 7:01 AM this morning.  To rule out my client, I also tried just using a regular HTTPS update from a web browser -- using https://myusername:mypassword@updates.dnsomatic.com/nic/update?hostname=all.dnsomatic.com -- which returns "good 67.84.xxx.xxx" however -- none of my hosts get updated to the new address.  IF I replace all.dnsomatic.com with one of my hostnames, that individual hostname WILL update.  But using all.dnsomatic.com is updating nothing.

 

Any ideas?

0

• 

  rotblitz December 01, 2016 18:13

  My suggestion is to open a support ticket with OpenDNS.  This seems to be account specific, and staff must check your account.

  One other idea I would have is to leave out the hostname completely:

  http(s)://updates.dnsomatic.com/nic/update

  0

  Comment actions Permalink
• 

  rickny December 01, 2016 18:17

  Well, the 2nd time I tried with the browser method, it did update all of them.. Now I'll have to backtrack and see if it is perhaps a client issue within OPNSense (I know I said pfSense earlier in error -- OPNSense is a fork of pfSense)

  0

  Comment actions Permalink
• 

  rickny December 01, 2016 18:20

  And now the OPNSense client appears to be working correctly as well.  Must have been a temporary issue.. FWIW -- I had cleared the OPNSense cached IP earlier as part of troubleshooting.

  0

  Comment actions Permalink
• 

  rotblitz December 01, 2016 18:21

  Well, it seems you're sorted!  Enjoy!

  0

  Comment actions Permalink
• 

  acrmartin June 28, 2020 16:08

  I know this is an old thread but I just encountered the same issue with pfsense complaining about bad characters etc.  I played around and it turns out, if you just enter updates.dnsomatic.com, it worked!

  0

  Comment actions Permalink

Please sign in to leave a comment.