import/export tool for DNS Records
imagine you get a domain with thousands of dns records and you have to create each by your self in plesk!!!
The ability to import and export DNS records was implemented as a separate extension called “Transfer of DNS Records”.
Check it out in the Extension Catalog for Plesk.
The extension works in Plesk Obsidian 18.0.33 and later.
—
AA
-
Ferran Romero commented
Of course, this feature should exist in a service for managing hosting....
-
Saad Masood commented
I was using WHM and cPanel for last 5 years until recently I heard about Plesk and found it fascinating that I actually switched over, but I was really sad to see Plesk have no import/export feature for DNS zone and it took me a lot of time to manually write new DNS zones. Having this feature will save a lot of time of users.
-
Kyle M commented
Very useful feature! Let's get this going :)
-
Dave commented
Prioritizing features based on a vote system makes sense for stuff that would be nice to see, not things like this which should be pretty basic functionality and obviously should be present in a hosting control panel.
-
Leonardo Gandini commented
still nothing.... why is it so difficult to add this?
-
Anonymous commented
useful for External Services e.g. Google Suite, MX records, Verification TXT Records, Comodo domain verification TXT Records etc.
-
Anonymous commented
DNS Configuration Import / Export / Backup
-
Gustavo Baetti commented
La verdad es que estoy decepcionado de la migracion.
1) resulta que tengo que entrar manualmente a cada server dns y cambiar la IP master del dominio porque el sistema no lo hace automatico
2) Y ahora me doy cuenta despues de migrar que no soporta la migracion de la libreta de correo y del calendario.
Podrian poner un CARTEL GIGANTE diciendo que antes de migrar hay que hacer una exportacion de la libreta o bien ya reparar este problema y sacar una version mejorada del migrador -
Jan van der Knaap commented
Why is this still not implemented. I run PowerDNS and want to migrate some zones to Plesk, manual just takes up too much time. I already have script that converts all PDNS domains to BIND but the domains are also stored in Plesks DB. If someone has a solution, please drop a line.
-
Anonymous commented
This would be very handy especially when working with Route 53 AWS
-
Anonymous commented
I see this is 4 years old basic function that saves at least 86 customers lots of admin time. To the developer some domain have 100 records and this is bind dns so there is no reason for not having a means to import zones/
-
Nicolas Mercado commented
Seriously this post is 4 years old?
As more SaaS have started to use DNS records for verification/configuration, moving a single domain into plesk can take almost a hundred manual actions.
Is it too hard to implement some sort of batch functionality to import a DNS import functionality to the GUI and let users correct any records before they are inserted in the PSA DB? -
ExecuServices commented
This is just basic functionality.
-
Tobias Gábríél Sörensson commented
This would be so useful so that we can say to users that they can import them themselfs. Please add this as soon as you can
-
Tomislav Kotulenko commented
Well, we often get zonefiles from our new customers who are transfering the domains and their webhosts to us. Mostly the customers have modified zonefiles with a lot of records. (one of the last ones hat over 200 various A Records) ... It takes much time until all the records are set manually.
creating a csv from zonefile takes a few minutes ...
-
Bryan S. Katz commented
I can't speak for the original poster, but I'd be using such a tool for cross-verification with other systems -- like my firewalls, my routers, and especially my backup/secondary dns server. I'd also use it when I spin up a new server -- also plesk-controlled, of course -- as a migration step. As always, CSV would be best. Yes I could certainly use CLI to do such things, but that's plesk-specific, and server-level migration issues, especially across plesk versions, are scary enough. They are always better with straight-up lists of values, without worrying that my ten-year old CLI commands are somehow out-of-date..