Since RouterOS v6.14 MikroTik offers a Dynamic DNS name service for RouterBOARD devices. This means that your device can automatically get a working domain name, this is useful if your IP address changes often, and you want to always know how to connect to your router.
The cloud service provides these services:
- ddns (provide dns name for router's WAN IPv4 and/or IPv6 address)
- approximate time (accuracy of several seconds, depends on UDP packet latency, useful when NTP is not available)
- time zone detection (if enabled, clock time zone will be updated even when DDNS and update time are disabled)
- Checks for outgoing IP address change: every 60 seconds
- Waits for the MikroTik's Cloud server's response: 15 seconds
- DDNS record TTL: 60 seconds
- Cloud time update: after reboot and during every DDNS update (when router's WAN IP address changes or after the
force-updatecommand is used)
- Time-zone-autodetect: The time zone is detected depending on the router's public IP address and our commercial database
After the device has sent its IP address to the MikroTik's Cloud server, it will stay on the server permanently. DNS name (/ip cloud ddns-name) will resolve to last sent IP address. When user sets
/ip cloud set ddns-enabled=no, then the device will send a message to MikroTik's Cloud server to disable the DNS name for this device.
/ip cloud set ddns-enabled=yes is set, then the device will send encrypted packets to MikroTik's Cloud server using port UDP/15252. For devices using RouterOS v6.43 and newer the encrypted IP/Cloud packets are going to be sent to cloud2.mikrotik.com. For devices using older RouterOS versions (prior to v6.43), encrypted IP/Cloud are going to be sent to cloud.mikrotik.com.
Since RouterOS v6.43 if your device is able to reach cloud2.mikrotik.com using IPv6, then AAAA record is going to be created for your public IPv6 address. If your device is only able to reach cloud2.mikrotik.com using IPv4, then only A record is going to be created for your public IPv4 address.
To enable and activate this service:
[admin@MikroTik] /ip cloud set ddns-enabled=yes [admin@MikroTik] /ip cloud print ddns-enabled: yes update-time: yes public-address: 118.104.22.168 public-address-ipv6: 2a02:610:7501:1000::2 dns-name: 529c0491d41c.sn.mynetname.net status: updated
To enable time update from cloud service:
[admin@MikroTik] > /ip cloud set update-time=yes
To enable automatic time zone detection:
[admin@MikroTik] > /system clock set time-zone-autodetect=yes
To manually trigger a DDNS update
[admin@MikroTik] > /ip cloud force-update
|ddns-enabled (yes | no; Default: no)||If set to
|update-time (yes | no; Default: no)||If set to
|public-address (read-only: address)||Shows device's IPv4 address that was sent to cloud server and assigned to DNS name (see dns-name). This field is visible only after at least one ddns-request was successfully completed.|
|public-address-ivp6 (read-only: address)||Shows device's IPv6 address that was sent to cloud server and assigned to DNS name (see dns-name). This field is visible only after at least one ddns-request was successfully completed.|
|warning (read-only: string)||Shows a warning message if IP address sent by the device differs from the IP address in UDP packet header as visible by the MikroTik's Cloud server. Typically this happens if the device is behind NAT. Example: "DDNS server received request from IP 22.214.171.124 but your local IP was 192.168.88.23; DDNS service might not work"|
|dns-name (read-only: name)||Shows DNS name assigned to the rdevice. Name consists of 12 character serial number appended by .sn.mynetname.net. This field is visible only after at least one ddns-request is successfully completed.|
|status (read-only: string)||Contains text string that describes current dns-service state. The messages are self explanatory
/ip cloud advanced
|use-local-address (yes | no; Default: no)||By default, the DNS name will be assigned to the detected public address (from the UDP packet header). If you wish to send your "local" or "internal" IP address, then set this to