/ip/cloud broken, domain mynetname.net expired and disabled

alaine · Mon Sep 06, 2021 4:45 pm

It seems that the domain mynetname.net expired a moment ago.

So, all /ip/cloud DDNS names have vanished.

I sent email Mikrotik support as it happened, and very exceptionally, also called a POTS call to their Riga switchboard. The switchboard is still very reluctant to connect to anybody, but as I repeated that the situation was critical, I asked her to write down the issue, word by word. Then she contacted their support, and after a short while, reported to me that they were (now at least) knowledgeable of the situation, and are working to fix it.

So, as of now (since 6-Sep-2021 10:49 UTC) many tons of businesses are down, tons of VPNs are down, and we are all waiting for the xxxxxx.sn,mynetname.net to start working nicely again.

This really is a major screw up by Mikrotik, I hope they will learn to maintain their production domains and other relevant services much much better.

For emergency resolving of DDNS names, you can ask directly from the mynetname.net NS-resolvers (159.148.147.201 and 2a02:610:7501

:201, 159.148.172.251 and 2a02:610:7501:4000::251). Not of course valid recourse in every case, but it does help for some of the emergent cases:

dig @159.148.147.201 dead42babe.sn.mynetname.net

si458 · Mon Sep 06, 2021 4:51 pm

i was just about to post this message, it completely stopped our monitoring as we rely on these names because the clients IPs change from one week to the next

# whois.PublicDomainRegistry.com

Domain Name: MYNETNAME.NET
Registry Domain ID: 1856616582_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.publicdomainregistry.com
Registrar URL: www.publicdomainregistry.com
Updated Date: 2021-09-06T10:48:10Z
Creation Date: 2014-04-29T08:21:38Z
Registrar Registration Expiration Date: 2022-04-29T08:21:38Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientHold https://icann.org/epp#clientHold
Registry Registrant ID: GDPR Masked
Registrant Name: GDPR Masked
Registrant Organization: GDPR Masked
Registrant Street: GDPR Masked
Registrant City: GDPR Masked
Registrant State/Province: 
Registrant Postal Code: GDPR Masked
Registrant Country: LV
Registrant Phone: GDPR Masked
Registrant Phone Ext: 
Registrant Fax: GDPR Masked
Registrant Fax Ext: 
Registrant Email: gdpr-masking@gdpr-masked.com
Registry Admin ID: GDPR Masked
Admin Name: GDPR Masked
Admin Organization: GDPR Masked
Admin Street: GDPR Masked
Admin City: GDPR Masked
Admin State/Province: GDPR Masked
Admin Postal Code: GDPR Masked
Admin Country: GDPR Masked
Admin Phone: GDPR Masked
Admin Phone Ext: 
Admin Fax: GDPR Masked
Admin Fax Ext: 
Admin Email: gdpr-masking@gdpr-masked.com
Registry Tech ID: GDPR Masked
Tech Name: GDPR Masked
Tech Organization: GDPR Masked
Tech Street: GDPR Masked
Tech City: GDPR Masked
Tech State/Province: GDPR Masked
Tech Postal Code: GDPR Masked
Tech Country: GDPR Masked
Tech Phone: GDPR Masked
Tech Phone Ext: 
Tech Fax: GDPR Masked
Tech Fax Ext: 
Tech Email: gdpr-masking@gdpr-masked.com
Name Server: ns1.suspended-domain.com
Name Server: ns2.suspended-domain.com
DNSSEC: Unsigned
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-09-06T13:49:56Z <<<

zktech · Mon Sep 06, 2021 4:54 pm

We are down as well. We use the mynetname.net to monitor all our customers routers devices.
This is beyond a big screwup. This should be set to auto renew. Hope they get it back up ASAP!

parham · Mon Sep 06, 2021 5:00 pm

here too 1.1.1.1 and 8.8.8.8 can't resolve but 4.2.2.4 can.

alaine · Mon Sep 06, 2021 5:09 pm

here too 1.1.1.1 and 8.8.8.8 can't resolve but 4.2.2.4 can.

DNS resolvers (like the 1.1.1.1) have already pretty much expired the zone-info for mynetname.net.

The NS servers for domain mynetname.net are:

159.148.147.201
2a02:610:7501:1000::201
159.148.172.251
2a02:610:7501:4000::251

One can make a DNS query directly to those authoritative main servers, they have the current and valid information, for example:

dig @159.148.147.201 dead42babe.sn.mynetname.net
nslookup  dead42babe.sn.mynetname.net 159.148.147.201

This semi-hack can help at least some of the cases, but by large, the DDNS system of the /ip/cloud is stil very much down.

wojo · Mon Sep 06, 2021 5:15 pm

mynetname.net has had many issues over the last year or two and this proven MikroTik does not treat is seriously. I liked how integrated it was, but moving everything I have to my backup service.

laurinkus · Mon Sep 06, 2021 5:15 pm

We are down as well. We use the mynetname.net to monitor all our customers routers devices.
This is beyond a big screwup. This should be set to auto renew. Hope they get it back up ASAP!

Same here. Our monitoring just started screaming about it.

cnt · Mon Sep 06, 2021 5:16 pm

Domain mynetname.net is suspended. Whats happen?

RadAPl · Mon Sep 06, 2021 5:18 pm

Aaaaa... please fix ASAP

laurinkus · Mon Sep 06, 2021 5:21 pm

Domain mynetname.net is suspended. Whats happen?

Looking at WHOIS it doesn't seem like it has expired. But it definitely looks suspended. Somebody playing DMCA games?

$ whois mynetname.net
Domain Name: MYNETNAME.NET
Registry Domain ID: 1856616582_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.PublicDomainRegistry.com
Registrar URL: http://www.publicdomainregistry.com
Updated Date: 2021-09-06T10:48:09Z
Creation Date: 2014-04-29T08:21:38Z
Registry Expiry Date: 2022-04-29T08:21:38Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientHold https://icann.org/epp#clientHold
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS1.SUSPENDED-DOMAIN.COM
Name Server: NS2.SUSPENDED-DOMAIN.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-09-06T14:18:29Z <<<

voiceland · Mon Sep 06, 2021 5:23 pm

Unacceptable !!!!

si458 · Mon Sep 06, 2021 5:23 pm

MAYBE somebody forgot to pay the $35 to renew it for the year it would seem

Domain mynetname.net is suspended. Whats happen?
Looking at WHOIS it doesn't seem like it has expired. But it definitely looks suspended.

$ whois mynetname.net
Domain Name: MYNETNAME.NET
Registry Domain ID: 1856616582_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.PublicDomainRegistry.com
Registrar URL: http://www.publicdomainregistry.com
Updated Date: 2021-09-06T10:48:09Z
Creation Date: 2014-04-29T08:21:38Z
Registry Expiry Date: 2022-04-29T08:21:38Z

laurinkus · Mon Sep 06, 2021 5:24 pm

somebody forgot to pay the $35 to renew it for the year, it would seem

Did you have a look at expiry date by any chance before making such a conclusion?

si458 · Mon Sep 06, 2021 5:25 pm

somebody forgot to pay the $35 to renew it for the year, it would seem
Did you have a look at expiry date by any chance before making such a conclusion?

oh yeh, my mistake, seems somebody suspended the domain then? as it should renew in april not september

bms · Mon Sep 06, 2021 5:32 pm

we also have the problem. does anyone know if the problem is being worked on?

anav · Mon Sep 06, 2021 6:30 pm

Too funny another thread on subject created over an hour earlier and another 30 minutes before this one, wonder how many there will be for this snafu!!
viewtopic.php?f=2&t=178256

alaine · Mon Sep 06, 2021 11:55 pm

The domain mynetname.net expire on 2022-04-29T08:21:38Z
Simply mikrotik forgot to pay the $35 annual fee to publicdomainregistry.com

Stop speculating and writing idiocy and wait for the service to restore.

Ok?

now as the mynetname.net is still expired and disabled, you might want to learn that the original whois info was very clearly disabled today from 6-Sep-2021 10:49 UTC. After very tiny caching/TTL was there, but that also expired a long time ago.

So, buddy, now you are looking at the expired domain whois-info, for the parked/disabled domain info.

I do wish that Mikrotik engineers will work 24/365 to fix this, as this really screws up the Mikrotik infrastricture for quite many tens of millions of people and remote VPN users.

If you really feel that the "ou, not broken" is still valid, I can not resolve my FQDN xxxxxxx.sn.mynetname.net since exactly 6-Sep-2021 13:30 UTC, so yes, there definitely is a problem with the zone mynetname.net . And yes, this is a major issue, for tens of millions of people, around the (quite flat) earth.

rextended · Tue Sep 07, 2021 12:07 am

You are really an idiot if you believe in the flat earth and write that is expired.

The domain is not expired.

If you check the wois of
https://publicdomainregistry.com/whois/
that have the control of mynetname.net
Is clear than is only suspended, not expired or deleted:

Updated Date: 2021-09-06T10:48:10Z
Registrar Registration Expiration Date: 2022-04-29T08:21:38Z
Domain Status: clientHold https://icann.org/epp#clientHold
Name Server: ns1.suspended-domain.com
Name Server: ns2.suspended-domain.com

shaneau · Tue Sep 07, 2021 2:52 am

Bugger. Any official statement?

DoubleDB · Tue Sep 07, 2021 8:03 am

Any official info on when will the service will be back ?

ccto · Tue Sep 07, 2021 8:17 am

For mynetname.net , the domain status is clientHold

It is suspended by domain registrar.
ref.: https://www.icann.org/resources/pages/e ... 4-06-16-en

DoubleDB · Tue Sep 07, 2021 12:45 pm

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

Tue Sep 07, 2021 12:51 pm

It is a known issue, follow also our social media, to be up to date:
https://twitter.com/mikrotik_com/status ... 79521?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.

parham · Tue Sep 07, 2021 12:55 pm

It is a known issue, follow also our social media, to be up to date:
https://twitter.com/mikrotik_com/status ... 79521?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.

si458 · Tue Sep 07, 2021 1:20 pm

It is a known issue, follow also our social media, to be up to date:
https://twitter.com/mikrotik_com/status ... 79521?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.

Glad to hear you have acknowledged the issue and are sorting it out! Shame about the delay though to alert customers, more than 24hours

PiratePete · Tue Sep 07, 2021 1:56 pm

It is a known issue, follow also our social media, to be up to date:
https://twitter.com/mikrotik_com/status ... 79521?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.

Is there an easy way we can point our routers to another DDNS service so that we can restore connectivity in the mean time?

alaine · Tue Sep 07, 2021 2:09 pm

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.

Tue Sep 07, 2021 2:12 pm

It is a known issue, follow also our social media, to be up to date:
https://twitter.com/mikrotik_com/status ... 79521?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.
Is there an easy way we can point our routers to another DDNS service so that we can restore connectivity in the mean time?

yes

https://twitter.com/MagO_On/status/1434 ... 98817?s=20

raymercastillo · Tue Sep 07, 2021 2:32 pm

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

rextended · Tue Sep 07, 2021 2:37 pm

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.

i4jordan · Tue Sep 07, 2021 3:05 pm

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

rextended · Tue Sep 07, 2021 3:22 pm

If someone can contact already remote device for do that, do not require the cloud...

Tue Sep 07, 2021 3:27 pm

no, you do this on your device. then all remote cloud devices will resolve to correct IP.

rextended · Tue Sep 07, 2021 3:31 pm

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.

Tue Sep 07, 2021 3:37 pm

Yes, more or less it is correct, only cloud2.mikrotik.com is used for the fresh RouterOS versions.

rextended · Tue Sep 07, 2021 3:37 pm

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

anav · Tue Sep 07, 2021 3:41 pm

Maybe the mynetname.net shutdown affects not just small users.....
https://www.theregister.com/2021/09/02/ ... _1_outage/

( but I doubt they are using MT products

)

henrrym20 · Tue Sep 07, 2021 3:50 pm

As a quick fix add the following static FWD lines to your router:
Code: Select all
/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

No funciona

hgonzale · Tue Sep 07, 2021 4:07 pm

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

3firs · Tue Sep 07, 2021 4:09 pm

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.

hgonzale · Tue Sep 07, 2021 4:17 pm

Thank for being in my "side"....

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.

rextended · Tue Sep 07, 2021 4:19 pm

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

This is a clear indication that you and you customers can't do a good work.
Is not serious business rely on 3rd party dns, MikroTik or not,
Everytime you must have two or more way to do the things on correct way,
instead to rely on one sigle free servce.
For be more clear: you do not pay anything for use the free cloud servce, what you expect?
And really you have only one way to access remote device and is by third-party dns? YOUR FAULT.

HartZA · Tue Sep 07, 2021 4:26 pm

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

This is a clear indication that you and you customers can't do a good work.
Is not serious business rely on 3rd party dns, MikroTik or not,
Everytime you must have two or more way to do the things on correct way,
instead to rely on one sigle free servce.
For be more clear: you do not pay anything for use the free cloud servce, what you expect?
And really you have only one way to access remote device and is by third-party dns? YOUR FAULT.

Oh man I; 'd love to implement a workaround just tried this DNS static route and still getting nowhere slowly. Hey great help would be if you'd like point us idiotic noobs in the right direction that'd be sweet.

rextended · Tue Sep 07, 2021 4:29 pm

Easy easy easy easy:
WAIT for them to fix the problem.

sysf · Tue Sep 07, 2021 4:29 pm

It is a known issue, follow also our social media, to be up to date:
https://twitter.com/mikrotik_com/status ... 79521?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.

Were there any attempts made by the registrar to contact MikroTik to resolve the problem before suspending the domain? If not, it's probably time to switch registrar..

rextended · Tue Sep 07, 2021 4:30 pm

The whole truth will never be revealed.

HartZA · Tue Sep 07, 2021 4:43 pm

Easy easy easy easy:
WAIT for them to fix the problem.

Man don't you love it when its soo easy. Here you're screaming blue murder and having backup alternatives but when someone asks a genuine ok what other alternatives are there that would kick these blokes in the balls you run away. Ne izindinganiso eziphindwe kabili

Kaugar · Tue Sep 07, 2021 4:50 pm

As a quick fix add the following static FWD lines to your router:
Code: Select all
/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

Its not working for me. Still cant reach my router from domain.

rextended · Tue Sep 07, 2021 4:55 pm

(EN: With double standards)

jppotgieter · Tue Sep 07, 2021 5:17 pm

I have a RB2011IL-RM - Where do I go to add this?

As a quick fix add the following static FWD lines to your router:
Code: Select all
/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

misucatinas · Tue Sep 07, 2021 5:21 pm

I have a RB2011IL-RM - Where do I go to add this?
As a quick fix add the following static FWD lines to your router:
Code: Select all
/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

In terminal

Maarten200 · Tue Sep 07, 2021 5:48 pm

As a quick fix add the following static FWD lines to your router:
Code: Select all
/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

Awesome!
It works for direct xxxxxx.sn.mynetname.net, but not for cname records.
site.example.com -> cname to xxxxxx.sn.mynetname.net

Any solution for cname records?

Thanks!

pe1chl · Tue Sep 07, 2021 6:01 pm

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

It is a bit unclear what use it would be to set a DDNS name on a router that is behind CG-NAT. Usually you would be best off by having each customer router setup a VPN outbound, towards a central router you use for management.
Now of course you could have used a DDNS name for that central router (which is not behind CG-NAT) but that indeed is not a very good idea, it would be better to use your own domain name and a fixed address for that central router. If necessary by putting it in a VPS where you can get a fixed address.

mbaldini · Tue Sep 07, 2021 6:07 pm

It is a bit unclear what use it would be to set a DDNS name on a router that is behind CG-NAT. Usually you would be best off by having each customer router setup a VPN outbound, towards a central router you use for management.
Now of course you could have used a DDNS name for that central router (which is not behind CG-NAT) but that indeed is not a very good idea, it would be better to use your own domain name and a fixed address for that central router. If necessary by putting it in a VPS where you can get a fixed address.

I'm using this solution and I'm having very few problems, only wih a couple of customers using the ddns xxxx.sn.mynetname.net as target for a CNAME of their own domain to use an easier address for services like vpn (eg vpn.domain.net instead of IP or xxxx.sn.mynetname.net).

I'm waiting for the fix by Mikrotik staff, customers know about the problem, it the fix will take long time I'll have to add a new ddns and change the CNAME

jppotgieter · Tue Sep 07, 2021 6:28 pm

I am getting syntax error (line 1 column 11) when trying to add these and also expected end of command (line 1 column 5)

I have a RB2011IL-RM - Where do I go to add this?

In terminal

rextended · Tue Sep 07, 2021 6:32 pm

Because only @Rextended explain than is working only from 6.47 RouterOS that have added the support for extended Static DNS...

jppotgieter · Tue Sep 07, 2021 6:37 pm

Ugh seriously... none of the "quick fixes" are working. Nothing posted by the people with these codes are working....

We need STEP-BY-STEP instructions on exactly how to fix this...

rextended · Tue Sep 07, 2021 6:38 pm

2021-09-07T15:37:37Z
Now is working again.

hgonzale · Tue Sep 07, 2021 6:57 pm

Yes Mr. You are totally right.
I have in another customers the paid no-ip...... like in my office
But others doesn't want to pay it .... then. we have this

And yes, you are right.
Thank you

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

This is a clear indication that you and you customers can't do a good work.
Is not serious business rely on 3rd party dns, MikroTik or not,
Everytime you must have two or more way to do the things on correct way,
instead to rely on one sigle free servce.
For be more clear: you do not pay anything for use the free cloud servce, what you expect?
And really you have only one way to access remote device and is by third-party dns? YOUR FAULT.

pe1chl · Tue Sep 07, 2021 7:08 pm

I'm waiting for the fix by Mikrotik staff, customers know about the problem, it the fix will take long time I'll have to add a new ddns and change the CNAME

Hopefully by now you understand that the fix cannot be made by MikroTik staff but has to be made by DNS registrar staff, and MikroTik depend on their willingness to do so.

dankoj · Tue Sep 07, 2021 7:09 pm

Seems to be working now

pe1chl · Tue Sep 07, 2021 7:09 pm

Ugh seriously... none of the "quick fixes" are working. Nothing posted by the people with these codes are working....

We need STEP-BY-STEP instructions on exactly how to fix this...

You need to understand the rationale behind the fixes and the circumstances under which they would work.
Of course for them to work you need to use the MikroTik router where you make the change (NOT the one behind the DDNS name but the one you use to access it!) as a DNS resolver.
When you use newfangled stuff like DoH or DoT, or you use external DNS resolver like 8.8.8.8 or 1.1.1.1, OF COURSE the fixes are not going to work!

rextended · Tue Sep 07, 2021 7:10 pm

The fix not work on RouterOS prior to 6.47 because they do not have Static DNS support for forwarding...

Not worry, is solved.

Nixi · Tue Sep 07, 2021 7:11 pm

As a quick fix add the following static FWD lines to your router:
Code: Select all
/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

This work!

Who is online