Page 1 of 1
IP Cloud question
Posted: Mon Dec 17, 2018 11:48 am
by satman1w
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:
Code: Select all
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
Re: IP Cloud question
Posted: Mon Dec 17, 2018 12:00 pm
by joserudi
I have the same problem. +1
Re: IP Cloud question
Posted: Mon Dec 17, 2018 12:02 pm
by engmohamed01
I have The Same ,
any one can help ?
Re: IP Cloud question
Posted: Mon Dec 17, 2018 12:02 pm
by const
+1 russia
Re: IP Cloud question
Posted: Mon Dec 17, 2018 12:19 pm
by gotsprings
Seen this since Friday. Would really appreciate and update.
Re: IP Cloud question
Posted: Mon Dec 17, 2018 12:19 pm
by R1CH
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.
Re: IP Cloud question
Posted: Mon Dec 17, 2018 12:46 pm
by satman1w
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.
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 !
Re: IP Cloud question
Posted: Mon Dec 17, 2018 12:50 pm
by engmohamed01
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
Re: IP Cloud question
Posted: Mon Dec 17, 2018 1:09 pm
by engmohamed01
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.
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 !
its working fine after update now .
Re: IP Cloud question
Posted: Mon Dec 17, 2018 1:34 pm
by dirtonth
We have customers complaining about same issue...
Re: IP Cloud question
Posted: Mon Dec 17, 2018 1:35 pm
by nescafe2002
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
Re: IP Cloud question
Posted: Mon Dec 17, 2018 1:35 pm
by nmt1900
It seems to be "intermittent" problem - sometimes resolution of sn.mynetname.net works and sometimes it returns SERVFAIL...
Re: IP Cloud question
Posted: Mon Dec 17, 2018 1:41 pm
by dirtonth
Re: IP Cloud question
Posted: Mon Dec 17, 2018 2:15 pm
by satman1w
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?
Re: IP Cloud question
Posted: Mon Dec 17, 2018 2:20 pm
by normis
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.
Re: IP Cloud question
Posted: Mon Dec 17, 2018 2:34 pm
by jrjr
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,
Re: IP Cloud question
Posted: Mon Dec 17, 2018 2:37 pm
by qostechgl
is this official? any device with firmware below 6.43 will no longer be able to update ip with cloud ip?
Re: IP Cloud question
Posted: Mon Dec 17, 2018 2:44 pm
by driven
If you updated the implementation of the cloud service, why is the entire long-term branch broken including the latest release?
Re: IP Cloud question
Posted: Mon Dec 17, 2018 2:46 pm
by mpadmin
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?
Re: IP Cloud question
Posted: Mon Dec 17, 2018 2:48 pm
by mkx
Maybe the problem is with the long-term version only?
As @normis hinted: problem is there for devices with ROS <= 6.42 ... devices with ROS >= 6.43 are OK.
Re: IP Cloud question
Posted: Mon Dec 17, 2018 2:52 pm
by dirtonth
Normis,
We do not understand what's the resolution to this problem. We have a number of customers reporting issues this morning. Their mynetname dns is not resolving from anywhere. Their router (IP>Cloud) sometimes manages to update the ip, and some reports "Failed", but either or, their IP is not resolving when we ping the full hostname ([*sn*].sn.mynetname.net).
Please let us know what we should inform the customers to do.
Thanks
Re: IP Cloud question
Posted: Mon Dec 17, 2018 3:07 pm
by mpadmin
Maybe the problem is with the long-term version only?
As @normis hinted: problem is there for devices with ROS <= 6.42 ... devices with ROS >= 6.43 are OK.
OK, but all my routers are using RouterOS 6.42.10 (long-term) and I want to keep it that way. I need stable IP cloud service too.
Re: IP Cloud question
Posted: Mon Dec 17, 2018 3:11 pm
by qostechgl
Same situation here with 6.42.10 long term supporr... This needs to be fixed asap
Re: IP Cloud question
Posted: Mon Dec 17, 2018 3:46 pm
by satman1w
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.
Hi Normis,
But I did! My routers are all on last stable revision of ROS.(6.43.7)!
If everything works fine I should be able to resolve domain regardless of the specific router and I am unable to do so, whatever DNS server I use!
I have pasted the lookup answer in my fist post.
"
No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for mynetname.net "
regards
Re: IP Cloud question
Posted: Mon Dec 17, 2018 3:55 pm
by TedjeVanEs
I’m 12 hours flying away from that router. I need mynetname to be up to even access it. When wil cloud dyn dns be up again?
Re: IP Cloud question
Posted: Mon Dec 17, 2018 4:09 pm
by koolandrew
I am having the same issue. None of my routers using the cloud service are up, and many have a dynamic ip address; hence the need to use it, so i cannot even support it.
Pleaes make an announcement regarding this.
Re: IP Cloud question
Posted: Mon Dec 17, 2018 4:21 pm
by normis