I can’t resolve any mynetname.net addresses RN. Temp downtime/maintenance, or does a box need to be restarted somewhere?
The same happened to me. All services that use mynetname.net DNS are down
same.
Same here. First dreamhost DNS fail, it took them 3 hours to repair. And now xxx.sn.mynetname.net is not working.
Merry Christmas, but they should have some stuff working even tonight
Same here, down > 1hr so far
Hope someone gets it working asap
Is there an official way of notifying outage?
Is it the first time it happens? It got me worried and thinking of start using another solution for hostnames.
Well they don’t have geographically separated DNS:
ns2.kissthenet.net. [‘159.148.172.251’] [TTL=172800]
ns1.kissthenet.net. [‘159.148.147.201’] [TTL=172800]
and one doesn’t respond with correct data, and the other is non-responsive.
Sounds like they need to re-engineer and put a little redundancy into their DNS infra
cloud mikrotik not working 25/12/2023
Same here
Same problem with DDNS mynetname.net
Same here, i know last year something happened like this for some days, i hope this time it will be fixed fast.
I can’t understand how you give a service and that it doesnt work for hours without anyone to fix it.
Merry cristmas
Yes same here and no one responded from technical team and we are here losing our customers…
same here…
I have the same issue. After this problem occurred last year, I ended up hiring a redundant DDNS service, which I keep running via script. My routers are only online because of this redundant DDNS service.
Merry Xmas from Mikrotik, are they even aware of the issue?
The ns1 is down but ns2 seems ok, the following works fine for me to find the IP.
dig a xxxxxxxx.sn.mynetname.net @159.148.172.251
Perhaps ns2 was also down earlier, now at least I can reach my servers. Looks like they are doing a maintenance thinking everyone is looking kids unpacking / playing with their Xmas gifts.
Seems to be back now?
Not sure… just tested and can’t get an IP for both ns1 and ns2.
% dig a ns1.mynetname.net @1.1.1.1|grep A$
;ns1.mynetname.net. IN A
% dig a ns2.mynetname.net @1.1.1.1|grep A$
;ns2.mynetname.net. IN A
% dig a ns1.mynetname.net @159.148.172.251
;ns1.mynetname.net. IN A
This looks worst now.
ns2.kissthenet.net seems ok for now
my IP->Cloud hostnames are working now, the ones like .sn.mynetname.net
We will wait some news from mikrotik, anyway, this is a free service, I do not expect 100% uptime.
There is no such thing as ns1.mynetname.net or ns1.mynetname.net
The 2 authoritative NS listed for that domain are ns2.kissthenet.net. (159.148.172.251) and ns1.kissthenet.net. (159.148.147.201)
They both resolve on IPv4 and IPv6
I am curious did the MT BTH resolver also fail??