IP Cloud domains mynetname.net down again?

RouterOS General
1

Hello Mikrotik,

Not sure where to report this, but one of the two nameservers that answer your /ip/cloud ddns results for mynetname.net appears to be misconfigured. It’s responding with nxdomain for names that should exist.

Cloud/DDNS is not working *urgent*
2

It’s unstable again. Twice in a week. Definitely going to look for a different solution for domains.

3

We are also seeing resolution issues on our side to a bunch of different units. It’s intermittent, so we still investigating where the fault might actually lie.
PS: We have also identified some issues with some ISPs towards Cloudflare services, it may be related but could also be co-incidental.

4

Is IP Cloud down right now? None of my domains resolve

5

Yes, down for me as well

6

Down again., but not all. but most

7

Seems, the dns servers are down.

There are two dns servers for mynetname.net:
ns1.kissthenet.net und ns2.kissthenet.net. Both are pingable but are not answering dns queries.:

# dig ns mynetname.net @192.33.14.30

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16 <<>> ns mynetname.net @192.33.14.30
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55171
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 5
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mynetname.net.                 IN      NS

;; 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

;; Query time: 7 msec
;; SERVER: 192.33.14.30#53(192.33.14.30)
;; WHEN: Tue Jul 02 09:38:22 CEST 2024
;; MSG SIZE  rcvd: 177

# dig ns mynetname.net @159.148.147.201

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16 <<>> ns mynetname.net @159.148.147.201
;; global options: +cmd
;; connection timed out; no servers could be reached

# ping 159.148.172.251
PING 159.148.172.251 (159.148.172.251) 56(84) bytes of data.
64 bytes from 159.148.172.251: icmp_seq=1 ttl=53 time=30.5 ms
64 bytes from 159.148.172.251: icmp_seq=2 ttl=53 time=30.4 ms
8

Ping “support@mikrotik.com”…

EDIT
Since there doesn’t seem to be any redundancy, we’re only using IP Cloud as a backup and have already migrated production to Cloudflare DNS.

9

02/07/2024 another DNS failure for the mynetname.net domain.
Mikrotik cloud problem. Still they can’t to have stable solution.

10

resolved for me at the moment

11

Rule of the internet: even for free services you receive (an excessive amount of) ingratitude. Friends, if you use mynetname in a professional context, your expectations/requirements for reliability are simply incorrect or not defined at all. Your fault - nothing to blame Mikrotik for.