Good day Lady's, Sir's, and LadySir's.
I am aware, that there is a dedicated topic for IP cloud. But that topic is dead since 2k19. So,
Can anyone please tell me, where can I find any information on "how to transfer assigned dns A record from one mikrotik to another"
I have one dying mikrotik (with too many bad blocks, on next reboot netinstall would not help). On that mikrotik I have a pptp server, wich is reachable by ddns record *.sn.mynetname.com.
I have several clients, who is connected to it by this DDNS A record. There is no option for re configuring those clients.
I can transfer all (server, ip, etc) configuration, but how I can transfer this particular DNS name?

You can’t, it’s tied to the serial number.

So basically I am fucked anyway. /thread

https://www.reddit.com/r/mikrotik/comme ... mynetname/

For new clients, use a CNAME in your own domain, pointing to the actual *sn.mynetname. For existing clients, there is really no way except reconfiguring them. If you are only afraid of losing connectivity during reconfiguration but you do have management access to them while the VPN connection is up, you can create a static DNS record for the old *sn.mynetname on those clients themselves and run a script on them to update the static record with the IP address obtained via the new *sn.mynetname (assuming the IP is changing dynamically, as otherwise you wouldn't need the *sn.mynetname at first place). If you have no management access to them, you're really f.a. as you wrote.

The advice in the previous post about using DNS CNAME records is the best way to move forward with a point of reference which you can control independently of any IP cloud entry tied as a specific piece of Mikrotik hardware.

However... as you state your current Mikrotik is "dying" rather than "dead", there is another way...

After you set up the new device with the required services, just connect the existing device behind the new device.

If you ensure that the "Use Local Address" option is NOT ticked/selected, then the original device will still update its own .sn.mynetname.net DDNS entry with whatever public IP address it connects to the DDNS server over the Internet with, allowing continued update to the original hardware-specific DDNS entry.

You state that there is no option for reconfiguring those clients, but hopefully that is just in the short term and you will be able to find a way to re-point those clients over to a new hardware-independent CNAME entry... This option should certainly give you more breathing time.

Hopefully the removal of services from the original device should extend its life and you can always disable as many services as possible and also disable all logging & graphing directly onto the devices internal memory to further reduce the number of writes to that internal flash.

Good luck!

...
After you set up the new device with the required services, just connect the existing device behind the new device.
...

This is a genius idea, I'm so disappointed it didn't come to my own mind. The only danger is that some devices periodically rewrite their flash chips to prevent them from losing the information (a clever idea otherwise, I've seen too many non-Mikrotik devices mysteriously not coming up after power outage due to flash chips losing their data), so even if you stop changing the configuration and disable graphing and logging to "disk" on the old device, it may still be a temporary solution.

@Sindy - Isn't the purpose of this forum to become the "Hive Mind" of Mikrotik knowledge and experience?

I know that I have certainly benefited from the invaluable advice you have shared yourself, over many, many posts.

Anyway - this is all about buying time, rather than becoming a permanent fix.

Awkwardly extending the cloud analogy of "servers as cattle not pets" the value is in the config and the services running on the Mikrotik hardware, rather than the devices themselves.

(Having written that, my lab with racks of servers and Mikrotik devices clearly expose my personal hardware fetishes...)

R

I too am deeply disappointed in you Sindy!
I may have to resign from the Sindy Fan Club................................ Just kidding!!!