Migration Manager changing DNS records...

[travisbell@]

Hey guys,

On my source box, a bunch of domains have custom DNS records setup. You know, things like sub-domains pointing to other IPs, etc...

When I migrate these domains, the IP address is getting changed to the new Plesk box instead of keeping them set to the IP on the source box. Can anyone explain to me why this is? Obviously, this is causing me some serious headaches...

Thanks!

 

[OZyryanov]

Hello!

What IP mapping do you have during migration?

Thanks.

 

[travisbell@]

I am just leaving it as default, ie. whatever Plesk is assuming to use for the shared IP.

Here's the thing, I just want every "X" IP to be changed and otherwise, leave everything else alone. How can that be done?

 

[OZyryanov]

All ip addresses in the ip mapping (Page Ip mapping) will be changed during migration.

 

[travisbell@]

Right, but IPs that are _not_ listed in the IP mapping are also being changed. It's really quite random and buggy to be honest, I have some accounts where the IPs stay the same as they are on the source box, but other accounts that do get changed.

Is there a known bug? Or way of fixing this?

 

[OZyryanov]

Where you migrate from?

 

[travisbell@]

Plesk 8.6.

 

[OZyryanov]

Could you answer what is mean "like sub-domains pointing to other IPs" - it is the real Plesk subdomain?

 

[travisbell@]

No, they are just DNS A records.

xxxxx.domain.com -> xxx.xxx.xxx.xxx

Although, I could check to see if the ones causing problems are Plesk created sub-domains that had their IP changed... that could be why this is happening...

 

[raaqi]

I've recently migrated from 8.3 box to 8.6.... one site did not preserve the custom DNS, but the rest did. so im not sure what the G-O is with yours. Sounds buggy

 

[OZyryanov]

I could not see a problem.

Please look for log file. Please look at dump file (is there an infomation about these dns-records in it).

Tnanks.

 

[Amin Taheri]

it would appear that the domains no longer do a xfer of the dns records and just are recreated using the new tempalte, at least in your case. I dont personally use dns on the web servers as we have a centralized dns farm for those purposes but it would be easy for others to verify and if verified to put in a bug report that psa staff will just reclassify as a feature request and fix in 6 months.

 

[by88]

Same problem here after about 5 months

We are experiencing exactly the same problem migrating more than 1000 domains from 8.0.1 to 8.6.

Some domains have "standard A records" (domain.tld, mail.domain.tld, webmail.domain.tld) customized and they have not been retained after migration process and simply the new template has been applied even if these customized records had not the IP of the old server but they pointed to external servers.

This is clearly a bug because only the A records with old IP should be replaced with the new IP, all other records should be leave untouched.

I have opened a ticket, now I hope Parallels provide a workaround to avoid hours of headache with manual fixing.

Enzo

 

[by88]

Parallels has closed the ticket in this way:

Unfortunately, current migration manager does not support custom DNS configurations. Consequently, to keep your personal settings you have either to change a DNS template before a migration for every group of domains of a single type or correct DNS settings manually after the migration is done. In later case, you can use either GUI or the dns utility of the command line combined with the script that can be found at

http://kb.odin.com/en/879

Here is my comments about it:

Have you an idea of what means to check and fix manually more than 1000 zones? it means hours of work and means errors.

this is a serious bug in the migration utility and after 5 months no one has taken care of it.
Why?

I can accept it for a free product but Parallels is not free.

Thank You

Enzo