• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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