hi! ip cloud mynetname is not working?? it´s not resolving 2h ago...
yep
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
When will the problem be solved?
Ask MT raising a ticket. We, users, have no clue.
seems it´s working again...
There are still problems in Central America.
It doesn't work in Bulgaria either.
Hi!
I encountered problems with resolving *sn.mynetname.net in particular my own recursive server couldn't get answer for it, but 1.1.1.1 and 8.8.8.8 could. I see that nameserver for domain mynetname.net is
;; AUTHORITY SECTION:
mynetname.net. 172800 IN NS ns2.kissthenet.net.
mynetname.net. 172800 IN NS ns1.kissthenet.net.
;; ADDITIONAL SECTION:
ns2.kissthenet.net. 172800 IN A 159.148.172.251
ns2.kissthenet.net. 172800 IN AAAA 2a02:610:7501:4000::251
ns1.kissthenet.net. 172800 IN A 159.148.147.201
ns1.kissthenet.net. 172800 IN AAAA 2a02:610:7501:1000::201
and thing that this answer I got asking m.gtld-servers.net, so it is a Glue record in additional section.
But:
> dig SOA mynetname.net. @159.148.147.201
; <<>> DiG 9.20.11-0ubuntu0.2-Ubuntu <<>> SOA mynetname.net. @159.148.147.201
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51633
;; flags: qr aa rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 5
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1024
;; QUESTION SECTION:
;mynetname.net. IN SOA
;; ANSWER SECTION:
mynetname.net. 3600 IN SOA ns1.kissthenet.net. hostmaster.kissthenet.net. 1787636977 60 600 3600 60
;; AUTHORITY SECTION:
mynetname.net. 3600 IN NS ns1.kissthenet.net.
mynetname.net. 3600 IN NS ns2.kissthenet.net.
;; ADDITIONAL SECTION:
ns1.kissthenet.net. 3600 IN A 159.148.147.201
ns1.kissthenet.net. 3600 IN AAAA 2a02:610:7501:1000::201
ns2.kissthenet.net. 3600 IN A 159.148.172.251
ns2.kissthenet.net. 3600 IN AAAA 2a02:610:7501:1000::251
;; Query time: 96 msec
;; SERVER: 159.148.147.201#53(159.148.147.201) (UDP)
;; WHEN: Tue Aug 25 10:49:37 +05 2026
;; MSG SIZE rcvd: 273
> dig A ns1.kissthenet.net. @159.148.147.201
; <<>> DiG 9.20.11-0ubuntu0.2-Ubuntu <<>> A ns1.kissthenet.net. @159.148.147.201
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7099
;; flags: qr aa rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1024
;; QUESTION SECTION:
;ns1.kissthenet.net. IN A
;; Query time: 87 msec
;; SERVER: 159.148.147.201#53(159.148.147.201) (UDP)
;; WHEN: Tue Aug 25 10:49:49 +05 2026
;; MSG SIZE rcvd: 47
Nameservers itself do not have A records for ns1.kissthenet.net and ns2.kissthenet.net. It is wrong and should be fixed.
Also serials do not match:
> dig SOA ``kissthenet.net``. @159.148.147.201 +short
ns1.kissthenet.net``. ``hostmaster.kissthenet.net``. 1787637108 60 600 3600 60
> dig SOA ``kissthenet.net``. @159.148.172.251 +short
ns1.kissthenet.net``. ``hostmaster.kissthenet.net``. 1787637118 60 600 3600 60
Now it works! 
MikroTik IP Cloud / DDNS appears to be down again today, September 7, 2026.
Multiple routers on different ISPs and RouterOS versions are affected. /ip cloud print stays at status: updating..., and *.sn.mynetname.net hostnames do not resolve from different networks/countries.
Looks similar to the August 24 outage.
Can anyone else confirm?