Question: Howto get IPv6 DDNS working on 6.43 cloud service

RouterOS General
1

Hi,

can please someone point how to configure the /ip cloud service to resolve IPv6 address?

I am running 6.43 on CHR and IPv4 resolves well. IPv6 is learned via DHCPv6 on the PPPoE interface where IPv4 is bound to.

Thanks,
dksoft

2

you can check now if your router has updated AAAA entry properly.

3

How do we disable IPv6 in /ip cloud?

Edit: This seems to work well:

/ipv6 firewall address-list
add address=cloud2.mikrotik.com list=cloud
/ipv6 firewall filter
add action=drop chain=output dst-address-list=cloud
4

for IP Cloud to get your external IPv6 address it has to have a connection to cloud2.mikrotik.com via IPv6.

*) you block in fireall cloud2.mikrotik.com IPv6 addresses (that is not that good, because IPv6 still could be used for DNS requests and ns1 and ns2 for ddns names uses same IP addresses.
*) You block that or you add static IPv4 cloud2.mikrotik.com in ‘/ip dns static’ router will not be able to resolve the IPv6 address and will not be able to connect.

5

I am hosting several IPv4-based services behind my MT using mynetname.net as hostname. IPv6 breaks these services.
To restore functionality I have to disable IPv6 Cloud and the posted solution does exactly that.

Edit:
Re-read your answer; you’re explaining that mynetname.net DNS lookups over IPv6 will fail.
This would be the case if you have a stand alone dns resolver using root hints which the MT does not.
When using a DNS forwarder, either internally or externally, the output chain will not be hit.
Therefore I don’t see any practical objections dropping these requests.

Adding static IPv4 entries for cloud2.mikrotik.com would lead to problems if MT decides to relocate IP Cloud service.

6

Back to the initial topic that IPv6 is not resolved: it suddenly works.
I don’t know why, but the public-address-ipv6 is now displayed and resolved.
It might be solved as I disabled and re-enabled the ip cloud ddns service as recommended in the Wiki.

Anyway, I am happy.