Nice new feature 
What is it?
enable it and you will see 
The Cloud service consists of a DDNS server for your router, and a time server. With a simple command, you can configure your router to receive a free domain name.
Router router can get a free domain name, so that you can connect to it, even if it has a changing IP address. No longer you have the need to learn scripting or sign up for 3rd party services to always have access to your router. Simply enable this feature, and the router will always inform the MikroTik DNS service of any IP address changes, so that you can always connect to it, even if your IP address has changed.
Some uses for this are:
• Set up a secure connection to your home network using PPTP, SSTP or IPSec for use when you need to connect to your home network from somewhere on the Internet
• Watch a security camera on your home network
• Copy files from your home network NAS
• Manage your router
Nice. Thank you
Ideally it should be based on trigger eg. DHCP renew, interface up, time server should stick to ntp client with default configuration enabled and pointed to public pool
Sent from my iPad using Tapatalk
time server will not be used, if you use NTP
GR8 Feature.
But What about NAT Networks, how we could get Ddns.
If your router sits behind NAT and does not get a public IP, then you would never have access to it anyway without the NAT router providing port forwards to you.
The cloud service reports to Mikrotik servers whatever public IP address it comes from. It does nothing to enable services in your mikrotik, just provides DNS name for your router if you have dynamic IP from your provider.
The question evidently was about 1:1 nat where all ports are redirected to the router’s wan behind other nat. Therefore the wan is not equipped with public IP. Does it work in this case?
DNS resolves to the public router, connection is made to this IP, 1:1 NAT should work on your gateway, if you want to redirect these requests to some internal machine.
The cloud DNS will be of course not useful for routers that have no public IP
Thus, not interesting for me so far. My ddns scripts work reliably in all cases…
of course you can still use DDNS scripts. But in this case, you only need to set one setting. No registration, no maintenance, no scripting.
Thank you Mikrotik Team!
Nice feature!
Without any scripts now VPN setup and access to my devices with dynamic IP.
I agree. Can be useful for many home users. Like torrent or edonkey clients, webservers, databases… Whatever. I would like to have syslog server, for instance. Or rrd tool for graphing directly in routers. Or at least dude running on mipsbe…
Hmmm.. I can’t find this option on x86.
It is not supported on x86.
See here.
Interesting and nice new feature!
One of those that simply makes everyday life a little bit easier!
Well,
Even I was sceptic, I have tried it…
Still I do not uderstand how Mikrotik could release such stupid thing:
- It does not recognize the internal ip range (defined by RFC)! There should be check in order to prevent local IP registrations.
- It writes something as message in the left side of statusbar:
" DDNS server received request from IP 8…". Dammed, why it is cut?? Why it is impossible to see the status message? - It gives terrible domain name. I would like to meet some people that will be able to write this address into the browser from memory when they are woken up in the middle of the night. If it is aimed at “home users” than this is not an advance for them.
- No multiple wans handling.
- Not working in case of 1:1 nat or dmz. Many of home users do not have public ip on their wan ports, but somehow natted, if ISP allowed this.
Why mikrotik did not get inspiration from DDNS agents in OpenWRT or from TP-Link routers? There is possible to drill-down the list of DDNS providers and fill simple few fields with username, domain and passowrd and it is? Mikrotik could select few mostly used DDNS service providers, create scripts, prepare the user interface cockpit for it and it would be much better. Of course, there could be added option to simply register, or to use mikrotiks own service, but in some user-friendly way. And adding new and new DDNS providers as users repot them. This could be helpful.
Really, really it looks very unprofessional. I am disappointed that (according to my oppinion) so highly valuated development team of mikrotik did something like this.
Isn’t this funny?:
[me@myrouter] > ping 30xxxxxxxxxxx.sn.mynetname.net
HOST SIZE TTL TIME STATUS
192.168.1.91 56 64 0ms
192.168.1.91 56 64 0ms
192.168.1.91 56 64 0ms
192.168.1.91 56 64 0ms
192.168.1.91 56 64 0ms
sent=5 received=5 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms
- It kind’a does AFAIK… I mean, there’s a warning if the public IP detected is different than the one the router sends. The “warning” is in the form of a status message.
- Can’t you resize the window to make the message fit?
- Anyone (home user or otherwise) can bookmark that name. The point of this feature is to keep the “pointer” to the router permanent, which would not be the case if your public IP changes. More professional users could add a CNAME record to a different domain that they own, and map that new name to name given here.
- OK, that one’s a bummer indeed, though I guess to handle that case, the name would become even less memorable, as it would need to contain an interface identifier (perhaps the default name of the interface, for the sake of permanence).
- While I haven’t yet tried out this myself, from reading the docs, it appears that those should be updated successfully… but with a warning, as pointed out. You’re saying that part doesn’t work as advertised?
Why mikrotik did not get inspiration from DDNS agents in OpenWRT or from TP-Link routers? There is possible to drill-down the list of DDNS providers and fill simple few fields with username, domain and passowrd and it is?
I can tell you from personal experience that it’s VERY difficult to ask from an end user to register any sort of an account for anything, particularly when they can’t wrap their head around why it’s necessary when they aren’t going to be manipulating a thing themselves (but instead let a machine do it for them). The logic goes that if something is publically visible, and you’re only setting it up once, it shouldn’t require an account, but just a one time request & approval process at worst… It takes some deep mental processing power for end users to figure out that a machine is doing something that they must otherwise do manually themselves (and thus they need to identify themselves, and not the device), and that the device needs a username and password in order to work on their behalf.
Of course, then again, RouterOS isn’t used so often by non-techie end users (yet?), so registering an account wouldn’t be a hard thing for most RouterOS users to do, so point taken there.
- It gives terrible domain name. I would like to meet some people that will be able to write this address into the browser from memory when they are woken up in the middle of the night. If it is aimed at “home users” than this is not an advance for them.
Easy solution:
CNAME: mikrotik.mydomain.com → 1234567890.sn.mynetname.net
Thanks for a handy feature! Hopefully it sees more refinement to add the ability to specify which Public IP(s) are ddns’d, and the ability to revoke/delete a domain.
I too use my own scripts for DDNS, but this is a very nice feature for those times you just want a domain and don’t need any fluff.