@normis I've been upgrading both RouterOS and Firmware to the latest current-channel version on all my devices and today the service is not working.Upgrading will make it work again + give some new features. Name will stay and nothing else will change.
[admin@xxxxxxx] > /ip cloud print ddns-enabled: yes update-time: no public-address: xxx.xxx.xxx.xxx public-address-ipv6: xxxx:xxxx:xxxx:xxxx::x dns-name: xxxxxxxxxxxx.sn.mynetname.net status: updated
Google:C:\Users\User>nslookup - 188.8.131.52
Default Server: one.one.one.one
*** one.one.one.one can't find 449xxxxxxxxe9.sn.mynetname.net.: Server failed
nslookup - 184.108.40.206
Default Server: google-public-dns-a.google.com
Confirmed that Google DNS is resolving the 6.43.x new IP cloud names but not Cloudflare DNS from here as well.There is a difference between DNS resolvers:
Firmware is 6.43.2 on CCR1036-8G-2S+ for example. This looks like connectivity problems, and nothing to do with old/new.
same issue here (this is 18hours now). Ive updated some routers from 6.42.7 to 6.43.7 (to new cloud system as directed) , but the issue is the same. the problem is that myhnetname.net WILL NOT resolve (ie a dns problem , not a /ip cloud problem).
this is really unacceptable- only because ip cloud has been nothing but problems from its release, and more importantly many people have made mikrotik well aware of this over the past 1-2 years since /ip clouds release. So mt has had plenty of time to fix or address /ip cloud (which frankly is not a very complicated system, and should be faility easy to make robust and stable), action only seems to have been taken in the past few months.
just search the forums people have been complaining about ip cloud non-stop (and i have reported issues to support many times). granted the problems have always been timeouts/updating and not dns resolution as it seems to be currently, but its still all related to a poor service/implementation and a stubbornness to address it.
@tricksol, as I said before, my routers and CHR were updated before this issue happened. I also rebooted some of my routers and nothing happened.@martinclaro It takes about 15 minutes for it to start working again once you upgrade
Looks like a miss configured DNSSEC and/or bad resolver...I wonder if there might actually be two separate problems at play here.
Do you have any plans for stable cloud on long-term (6.42.10)? You urge us to 6.43, but I want to use long-term. Or maybe long-term will be renamed to short-term?Not entirely sure. Within today it should return.
But I urge the v6.42 and older users to upgrade to v6.43. It's very stable right now. The new v2 cloud is hosted in our new Tier 2 data centers. The old one ... not so much.
@normis!!! Could you confirm the following ???What specifically is not working? Was it ever working before ?6.43.7
So it is no longer needed to disable cloud before upgrading to 6.43+ and then re-enable it for it to use new cloud?Both are working right now.
v6.43 and newer automatically uses new cloud.
More info: https://wiki.mikrotik.com/wiki/Manual:IP/Cloud#Services