Tomato & DNS-O-Matic

Featured

Follow

Brian Hartvigsen

March 26, 2015 18:19

It appears the update to DNS-O-Matic's SSL certificate after the Heartbleed SSL vulnerability has broken Tomato's ability to send updates over SSL.  The current fix for this is to switch to a Custom URL format and use HTTP based updates. Use the URL below replacing %USER%, %PASS%, and %HOST% with the appropriate information for your account:

http://%USER%:%PASS%@updates.dnsomatic.com/nic/update?hostname=%HOST%

You can still use all.dnsomatic.com for %HOST% to update all your configured services.

Note: Due to how Tomato processes the URL you must use a username, not your email address.

0

• 

  lejurassien April 27, 2017 14:41 (Edited April 27, 2017 14:47)

  
  
  Today it's no more needed..

   

   

  1

  Comment actions Permalink

Please sign in to leave a comment.