Migrator doesn't adjust DNS properly (certain conditions)

[TomBoB]

Username:

TITLE

Migrator doesn't adjust DNS properly (certain conditions)

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.61 Update #5; AlmaLinux 8.10; Migrator 2.25.5-3397

PROBLEM DESCRIPTION

Migrate a customer (or subscription) from another Plesk server with same setup.
Website hosting of subscription in question is elsewhere off Plesk; A and AAAA for domain point to another server. Only used for emails hosting.
On target server, DNS for A records [for mail. webmail.] are adjusted to new target server. The AAAA records are not adjusted and stay the settings as they are on the source server. If the SPF record of the source subscription includes the source servers IPv6, it also stays that of the source server and is not adjusted to the one of the target server.

STEPS TO REPRODUCE

Set up domain. Have A and AAAA for main domain point to some other server off Plesk. Have A and AAAA records for mail. and webmail. point to Plesks own IPs. Have mail set up properly as per default Plesk setup.
Migrate subscription.
Check DNS settings on target sever after migration.

ACTUAL RESULT

; A RECORDS
mail IN A <target server IP>
webmail IN A <target server IP>

; AAAA RECORDS
mail IN AAAA <source server IP>
webmail IN AAAA <source server IP>

; MX RECORDS
@ IN MX 10 <FQDN Plesks hostname>

; TXT RECORDS
@ IN TXT v=spf1 mx ip4:<target server IP> ip6:<source server IP> ~all

EXPECTED RESULT

; A RECORDS
mail IN A <target server IP>
webmail IN A <target server IP>

; AAAA RECORDS
mail IN AAAA <target server IP>
webmail IN AAAA <target server IP>

; MX RECORDS
@ IN MX 10 <FQDN Plesks hostname>

; TXT RECORDS
@ IN TXT v=spf1 mx ip4:<target server IP> ip6:<target server IP> ~all

ANY ADDITIONAL INFORMATION

The server wide default for the MX record is mail.<domain>

For the subscriptions that have the webhosting pointing elsewhere and only provide email hosting, the MX record for those domains is manually set to the Plesks hostname as FQDN.

Happened on three different occasions during the last week. All with above domain setup. Not sure if the non-standard MX entry plays into it.

Have corrected it manually each time, but would be nice if this glitch can be ironed out.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Kaspar@Plesk]

@TomBoB what are the IP addresses distribution types on both servers? Are the IP's configured as shared or dedicated (in Tool & Settings > IP Addresses)? And is it the same for both servers?

 

[TomBoB]

Hi, both IPv4 and IPv6 are shared. Same on both servers.

 

[Kaspar@Plesk]

@TomBoB thank you! Unfortunately I can't replicate the issue, but it seems plausible that this could happen. I trying to figure out what specific conditions could cause this behavior so this issue can be replicated.

Can you perhaps post what your DNS template looks like (Tools & Settings > DNS Settings)?

 

[TomBoB]

Hi, the DNS template in use on both source and target server:

<domain>. A <ip>
<domain>. AAAA <ipv6>
<domain>. MX mail.<domain>.
<domain>. TXT v=spf1 mx ip4:<ip> ip6:<ipv6> ~all
<domain>. NS kehlani.ns.cloudflare.com.
<domain>. NS leo.ns.cloudflare.com.
<domain>. CAA letsencrypt.org
_dmarc.<domain>. TXT v=DMARC1; p=reject; adkim=s; aspf=s;
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
mail.<domain>. AAAA <ipv6>
webmail.<domain>. A <ip>
webmail.<domain>. AAAA <ipv6>
www.<domain>. CNAME <domain>.

However for the domains in question where the issue happened, the MX records was manually adjusted to be Plesks FQDN [example] ourserver3.ourcompany.com as the websites A and AAAA record point to [example] wix servers.

 

[Kaspar@Plesk]

Thank you, I apricate the extra info. Unfortunately I am still unable to replicate the issue, which makes it hard to investigate. I don't doubt there is an issue tough. Any chance you can open a ticket for this with our support team for an investigation by our engineers on your server?

 

[TomBoB]

Don't have another migration of that kind to do for the moment. Will ask permission and contact support when the next one comes up. Thanks for looking into it!