• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Migration between plesk 12 servers, error with dns configuration

SalvadorS

Regular Pleskian
Hello,

Yesterday I migrated a domain with the migration tool from a Debian 7.6 Plesk 12.0.18 MU35 box to a Debian 7.6 Plesk 12.0.18 MU35 box

This domain have a simple DNS configuration. The A registry for the domain.com was an own IP instead the IP of the server. Rest of the DNS configuration was the same.

After migration the A registry for the domain.com was an own IP too (as expected) but also the A registry for mail.domain.com

Before migration, in the old server:

A domain.com x.x.x.x (own ip)
A mail.domain.com y.y.y.y (server ip)

After migration, in the new server:

A domain.com x.x.x.x
A mail.domain.com x.x.x.x

The migration had changed the IP for mail.domain.com for the IP of the A registry for domain.com

Very strange. I double-checked it (as the domain in the "old" server was suspended)
Clien´t don´t have access to the control panel, so no changes done.
 
I'm guessing this is sort of expected. The migrated domain is recreated to use the appropriate settings for having an exclusive IP.

I would guess that if y.y.y.y had been an external IP, it would not have been changed.

The thing that may have triggered this is the domain being suspended, but it may have happened anyway.

I guess it depends on how the logic for detecting if an IP is "custom" or not works during the migration/recreation process. But that's only a guess.
 
Mmm, I expected after a migration that nothing changed. In this case, the mail of the client stopped to work. I don´t know if this a unique case or if it is a bug, but in a migration you (plesk migration tool) can´t change the dns configuration...

In my case, some client have this configuration (websites in other services and mail with us)
 
Ah, not I had not expected mail to stop working. And you are right of course - it shouldn't happen.

I would love to know if it was due to the domain being disabled. My thinking is that, at one time, migrating a disabled domain did not migrate, for example, database users. This was a bug fixed long ago. But I'm wondering if something similar is happening here.
 
The domain was disabled in the original server only after the migration.

I keep an eye if this will happen in the future again...
 
Back
Top