IP Cloud question

RouterOS General
1

Hi,

What is happening with IP Cloud? None of my routers are able to update their addresses.
mynetname.net cannot be resolved…

Since a few of my tunnels depend on this, I would like to know, what is happening.

Thanks


nslookup says:
C:\Users\user>nslookup mikrotik.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: mikrotik.com
Addresses: 2a02:610:7501:1000::2
159.148.147.196


C:\Users\user>nslookup mynetname.net
Server: google-public-dns-a.google.com
Address: 8.8.8.8

DNS request timed out.
timeout was 2 seconds.
*** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for mynetname.net

/ip cloud Error: request time out
2

I have the same problem. +1

3

I have The Same ,
any one can help ?

4

+1 russia

5

Seen this since Friday. Would really appreciate and update.

6

If you use an old RouterOS version, the service no longer works. Make sure to update your RouterOS, stop the IP cloud service then start it again.

EDIT: Actually it seems like a service outage, ns1.kissthenet.net and ns2.kissthenet.net are both failing.

7

Never mind the router and the ROS version (which is updated to actual revision btw…) but none of the DNS servers including 8.8.8.8 cannot resolve “mynetname.net”!
that is the problem !

8

when i try to ping from https://network-tools.com/
its give me
Unknown error: 1214
Unknown error: 1214
Unknown error: 1214
Unknown error: 1214
Unknown error: 1214
Unknown error: 1214
Unknown error: 1214
Unknown error: 1214
Unknown error: 1214
Unknown error: 1214

9

its working fine after update now .

10

We have customers complaining about same issue…

11

mynetname.net has no A or AAAA records defined, as your nslookup reveals.

Try [your_serial].sn.mynetname.net instead:

C:\>nslookup 000a09000195.sn.mynetname.net ns1.kissthenet.net
Server:  UnKnown
Address:  2a02:610:7501:1000::201

Name:    000a09000195.sn.mynetname.net
Address:  82.x.y.z
12

It seems to be “intermittent” problem - sometimes resolution of sn.mynetname.net works and sometimes it returns SERVFAIL…

13

Related Topic: http://forum.mikrotik.com/t/ip-cloud-error-request-time-out/125934/1

14

You are missing the point!
How exactly will I help google dns to be aware of mynetname.net if I upgrade router ??

The problem is that domain is not resolvable! None of the DNS servers are aware of it.

ok?

15

It will help. Because new RouterOS has a completely different Cloud implementation which uses DIFFERENT DNS SERVERS on MikroTik side. Please do what was suggested.

16

Hi,
On my own house router, with the latest long term version 6.42.10 it is was not working.
I tried with diferent dns servers on the router and rebooted the router several times and it still was not working
Them I updated to the latest stable version 6.43.7 and it started to work.
Best regards,

17

is this official? any device with firmware below 6.43 will no longer be able to update ip with cloud ip?

18

If you updated the implementation of the cloud service, why is the entire long-term branch broken including the latest release?

19

Same problem for all my routers on dynamic IP addresses (all using RouterOS 6.42.10). My monitoring system are showing them down, DNS names cannot be resolved.

Since one week Cloud was very unresponsive (with many timeouts), today it just completely stop. Here is the NSLOOKUP results:

> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> XXXXXXXXXXX.sn.mynetname.net
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to google-public-dns-a.google.com timed-out

Maybe the problem is with the long-term version only?

20

As @normis hinted: problem is there for devices with ROS <= 6.42 … devices with ROS >= 6.43 are OK.