DynDns scripts HTTPS

RouterOS Scripting
1

I’m sure there is a reason why all the DynDNS update scripts are HTTP. Can anyone explain why HTTPS is not used?

cheers,
Jeroen

2

Because fetch didn’t support HTTPS.

3

Oh, didn’t? so it does know? (off checking the wiki). That’s too bad as I don’t feel like looking for another solution:))

Nope it still does not. Blast!

4

If you use the ChangeIP.com Dynamic DNS it will use SSL on RouterOS. the “/tool dns-update” uses SSL to our site whereas the ‘fetch’ command will not.

Sam

5

Hi Sam,

It just happens I already registered after a good look around on the forums here.
Are both the sending of username and password and the update secured with SSL? This is probably something Mikrotik support can answer, but would you happen to know whether the certifcate of your site checked by the router? SSL is just as secure as verifying you are indeed connecting to your site and to nowhere else. Don’t really know how I can check this. µ

At any rate, I did not feel comfortable using a non-secure Dynamic DNS service.

6

Sam,

Some code of the script did not really work out for me so I changed a bit of coded and added some. Do you see any issues or is this ok?

Next line of code yields an error:

#:global ddnsip [ /ip address get [/ip address find interface=$ddnsinterface] address ]

So I added:

:local network [/ip address get number=1 address]
#:log info (" network is $network")

:local length [:len $network]
#:log info ("length is $length")
:local ddnsip [:pick $network 0 ($length-3)]
:log info ("UpdateDynDNS: fetched IP address  is $ddnsip")

Which in turn required me to change:

This:

:log info [ :put [/tool dns-update name=$ddnshost address=[:pick $ddnsip 0 [:find $ddnsip "/"] ] key-name=$ddnsuser key=$ddnspass ] ]

to:


 :log info [ :put [/tool dns-update name=$ddnshost address=$ddnsip key-name=$ddnsuser key=$ddnspass ] ]