For mynetname.net , the domain status is clientHold
It is suspended by domain registrar.
ref.: https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en
Has someone called MikroTik offices about this? …
What is the phone number for office / support ? Maybe if we all start calling, they’ll actually get around to fixing it…
It is a known issue, follow also our social media, to be up to date:
https://twitter.com/mikrotik_com/status/1435138440870379521?s=20
domain is suspended because of abuse by user(-s) or bad actors, not because of forgotten payment. we are working with registrar to solve it.
Thanks Normis,
It would be great if someone from Mikrotik, to updating us yesterday, Hope you guys fix it soon.
Glad to hear you have acknowledged the issue and are sorting it out! Shame about the delay though to alert customers, more than 24hours
Is there an easy way we can point our routers to another DDNS service so that we can restore connectivity in the mean time?
Just to make sure:
If the current DNS registrar is acting up “due to suspicious DNS activity”, it might be a long way to get things settled with that provider.
By far, the best and fastest option here is to move the mynetname.net from the current (disabled) registrar to anybody else, even to Godaddy.
Now the old registrar will provide a transfer key right away, and the new registrar will take the domain. Now the mynetname.net has again working NS-resolvers, and the current issue will be cleared. This takes
usually about 15 minutes, as the policies and acting-outs of the old registrar are not moved to the new registrar.
I hope Mikrotik knows this, as negotiating with the old registrar might be slow, difficult and painful. This will clear the problems of us many tens of millions of Mikrotik DDNS users globally.
Greetings, what response time or reactivation of the mikrotik DNS will be activated, more than 100 vpn will be managed and I fully try the service down thanks to that problem, I would like to know what response time they will give us to solve the problem
When they have done.
You’re subtracting manpower to calculate the time it takes.
As a quick fix add the following static FWD lines to your router:
/ip dns static
add forward-to=159.148.147.201 regexp=".*\\.sn\\.mynetname\\.net\$" type=FWD
add forward-to=159.148.172.251 regexp=".*\\.sn\\.mynetname\\.net\$" type=FWD
And flush the DNS cache !
This forwards any query for *.sn.mynetname.net to DNS servers: 159.148.147.201 or 159.148.172.251
If someone can contact already remote device for do that, do not require the cloud…
no, you do this on your device. then all remote cloud devices will resolve to correct IP.
This mean that the REMOTE devices can correctly update the cloud?
For example REMOTE device contact cloud.mikrotik.com for update the DNS xxx.sn.mynetname.net?
I never investigated what domain are contacted to update dns.
Yes, more or less it is correct, only cloud2.mikrotik.com is used for the fresh RouterOS versions.
EDIT:
Ok, are used cloud2.mikrotik.com 159.148.172.251 159.148.147.201 and are both working.
Are the same nameserver used for ns.mynetname.net
Maybe the mynetname.net shutdown affects not just small users…
https://www.theregister.com/2021/09/02/aws_ap_northeast_1_outage/
( but I doubt they are using MT products 
)
No funciona
Hello. This is a nightmare… WOW… many customers complaining. Many are in GC-NAT (not real IP address) and then I can’t log on even knowing the real ip. Nightmare.. Routers in remote, isolated area, even in another countries… SHIT
I’m sorry but I couldn’t help but laugh at your response. I feel your pain, we are in a similar situation. Still no ETA and it’s ridiculous.