• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs DNS template placeholder aren't replaced with right IP address when using specific muli IP setup

skibidi

skibidi

New Pleskian
Hi,

As soon as I add a new domain, some DNS records don't reflect the selected IP addresses.

I was able to reproduce this behavior on a clean Ubuntu 22.04 installation with no custom configuration, and a freshly installed Plesk with the recommended installation method. It depends on 2 Plesk settings before adding a new domain:

1. Tools & Settings -> Mail Server Settings -> Outgoing mail mode: send from the specific IP addresses
  • select the main Server IP's
2. Tools & Settings -> DNS Settings
  • change the pre-configured DNS entry from "<domain>. MX mail.<domain>." to "<domain>. MX <domain>."

Afterward, any new domain will have the main server IP's mixed into the DNS zone instead of the chosen IP addresses. This means that the web server configuration cannot properly serve the content.

plesk001.png

The issue I'm experiencing with the default DNS template "mail.<domain>" is that the autodiscovery and manual configuration settings for any email do not match, it defaults to the domain itself when there's no custom domain name specified in the server-wide mail configuration (Tools & Settings -> Mail Server Settings -> Mail autodiscover), regardless of the DNS template. Additionally, when assigning a mail certificate in SSLit!, it is always associated with the domain itself and not with any subdomain, such as "mail.<domain>", even when the subdomain is specified in the DNS template.

Thanks for any help!
 
Just to be clear, for my understanding, this is a bug and not a feature request.

In short: Plesk is overriding the DNS template placeholders (see DNS Settings | Plesk Obsidian) "<ip>" and "<ipv6>" instead of "<ip.mail>" and "<ipv6.mail>".

The impact of this bug is: it creates wrong VirtualHost entries in the web server configuration, making the website inaccessible,

One possible way to fix this would be:
1. "<ip>" and "<ipv6>" should be unconditional in the DNS template
2. "<ip.mail>" and "<ipv6.mail>" conditional (the conditions are mentioned in my first post point 1 and 2)
3. document everything in DNS Settings | Plesk Obsidian

I will not get further into the email autodiscovery and SSLit! inconsistency (my last paragraph in my first post), which may have partly created this mess in the first place.
 
Despite @skibidi did not created a bug report (yet), I still feel this should be investigated further. I haven't tested this, but is seems like a bug if the <ip.mail> and <ipv6.mail> placeholders aren't replaced by the right IP address in a DNS zone.

I've moved the topic to the reports forum.
 
I made 5 test scenarios in an effort to provide a more comprehensive description.

1. Test scenario

Steps to reproduce
- Tools & Settings -> Mail Server Settings -> Outgoing mail mode: Send from the specified IP addresses:
IPv495.179.139.239
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
- Tools & Settings -> DNS Settings:
<domain>.A<ip>
<domain>.AAAA<ipv6>
<domain>.MXmail.<domain>.
mail.<domain>.A<ip>
mail.<domain>.AAAA<ipv6>
www.<domain>.CNAME<domain>.
- Domain -> Add Domain -> Blank website:
domain namev39.confidential.cloud
IPv495.179.136.198
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:198

Actual result
v39.confidential.cloud.A95.179.136.198
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A95.179.139.239
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.

Expected result
v39.confidential.cloud.A95.179.136.198
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A2a05:f480:1400:2cf8:5400:4ff:fe9a:198
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.

2. Test scenario

Steps to reproduce
- Tools & Settings -> Mail Server Settings -> Outgoing mail mode: Send from the specified IP addresses:
IPv495.179.139.239
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
- Tools & Settings -> DNS Settings:
<domain>.A<ip>
<domain>.AAAA<ipv6>
<domain>.MX<domain>.
mail.<domain>.A<ip>
mail.<domain>.AAAA<ipv6>
www.<domain>.CNAME<domain>.
- Domain -> Add Domain -> Blank website:
domain namev39.confidential.cloud
IPv495.179.136.198
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:198

Actual result
v39.confidential.cloud.A95.179.139.239
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A95.179.136.198
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.

Expected result
v39.confidential.cloud.A95.179.136.198
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A2a05:f480:1400:2cf8:5400:4ff:fe9a:198
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.
 
3. Test scenario

Steps to reproduce
- Tools & Settings -> Mail Server Settings -> Outgoing mail mode: Send from the specified IP addresses:
IPv495.179.139.239
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
- Tools & Settings -> DNS Settings:
<domain>.A<ip.web>
<domain>.AAAA<ipv6.web>
<domain>.MXmail.<domain>.
mail.<domain>.A<ip.mail>
mail.<domain>.AAAA<ipv6.mail>
www.<domain>.CNAME<domain>.
- Domain -> Add Domain -> Blank website:
domain namev39.confidential.cloud
IPv495.179.136.198
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:198

Actual result
v39.confidential.cloud.A95.179.136.198
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A95.179.139.239
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.

Expected result
v39.confidential.cloud.A95.179.136.198
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A2a05:f480:1400:2cf8:5400:4ff:fe9a:198
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.

4. Test scenario

Steps to reproduce
- Tools & Settings -> Mail Server Settings -> Outgoing mail mode: Send from the specified IP addresses:
IPv495.179.139.239
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
- Tools & Settings -> DNS Settings:
<domain>.A<ip.web>
<domain>.AAAA<ipv6.web>
<domain>.MX<domain>.
mail.<domain>.A<ip.mail>
mail.<domain>.AAAA<ipv6.mail>
www.<domain>.CNAME<domain>.
- Domain -> Add Domain -> Blank website:
domain namev39.confidential.cloud
IPv495.179.136.198
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:198

Actual result
v39.confidential.cloud.A95.179.139.239
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A95.179.136.198
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.

Expected result
v39.confidential.cloud.A95.179.136.198
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A2a05:f480:1400:2cf8:5400:4ff:fe9a:198
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.
 
5. Test scenario

Steps to reproduce
- Tools & Settings -> Mail Server Settings -> Outgoing mail mode: Send from the specified IP addresses:
IPv495.179.139.239
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
- Tools & Settings -> DNS Settings:
<domain>.A95.179.136.198
<domain>.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
<domain>.MX<domain>.
mail.<domain>.A<ip.mail>
mail.<domain>.AAAA<ipv6.mail>
www.<domain>.CNAME<domain>.
- Domain -> Add Domain -> Blank website:
domain namev39.confidential.cloud
IPv495.179.136.198
IPv62a05:f480:1400:2cf8:5400:4ff:fe9a:198

Actual result
v39.confidential.cloud.A95.179.139.239
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A95.179.136.198
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.

Expected result
v39.confidential.cloud.A95.179.136.198
v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
v39.confidential.cloud.MXmail.v39.confidential.cloud.
mail.v39.confidential.cloud.A2a05:f480:1400:2cf8:5400:4ff:fe9a:198
mail.v39.confidential.cloud.AAAA2a05:f480:1400:2cf8:5400:4ff:fe9a:198
www.v39.confidential.cloud.CNAMEv39.confidential.cloud.

Even in the 5th test case Plesk is overriding the hardcoded IP addresses in the DNS template.
 
Could you please try to reduce all the information to a simplified description? There are lots of records mentioned that don't seem to have anything to do with the actual issue.

I am also not sure whether this is a bug, because the records in a domain do not reflect the sender address setting. It just does not matter what is mentioned in a DNS record to set from which IP a mail is being sent as long as the IP is in some way associated with the domain.

I also need to ask you to please follow the form, that would be


PRODUCT/VERSION, OS/ARCHITECTURE

OS version, architecture:

Product version (including MU):

PROBLEM DESCRIPTION

STEPS TO REPRODUCE

[Please enumerate the steps to reproduce in proper formatting, e.g. 1: 2: 3:]

please be as precise as possible!

ACTUAL RESULT

EXPECTED RESULT

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Provide clear expectations!! what do you expect? answer for how-to? bug to be filled? documentation correction?

SUPPORT ACTIONS OF INVESTIGATION / RESOLVING

POSSIBLE TEMPORARY WORKAROUND

LOGS AND ANY ADDITIONAL INFORMATION
 
@Peter Debik it's really strange how Plesk handles placeholders and static entries in the DNS template. In our complex setup we need to change the MX record from "mail.<domain>." to "<domain>.", which initially triggered this unexpected behavior and led to inconsistent VirtualHost entries. As a workaround, we tried converting the placeholders into static entries, but Plesk still replaces them with the sender address during domain creation.

PRODUCT/VERSION, OS/ARCHITECTURE
Plesk Obsidian 18.0.56.0, Ubuntu 22.04.3 LTS

PROBLEM DESCRIPTION
DNS template placeholders (<ip>, <ipv6>, <ip.web>, <ipv6.web>) and static entries are replaced with mail sender address when using multi-IP's in Plesk.

STEPS TO REPRODUCE
Change mail sender address to other than customer domain IP, create a new domain, inspect DNS records.

e.g. 1
Change mail sender address to the main IP's: 95.179.139.239 & 2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
Change DNS template entry:
<domain>. MX <domain>.
<domain>. A <ip>
<domain>. AAAA <ipv6>
Create a new domain (v39.confidential.cloud) with the IP's: 95.179.136.198 & 2a05:f480:1400:2cf8:5400:4ff:fe9a:198

e.g. 2
Change mail sender address to the main IP's: 95.179.139.239 & 2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
Change DNS template entry:
<domain>. MX <domain>.
<domain>. A <ip.web>
<domain>. AAAA <ipv6.web>
Create a new domain (v39.confidential.cloud) with the IP's: 95.179.136.198 & 2a05:f480:1400:2cf8:5400:4ff:fe9a:198

e.g. 3
Change mail sender address to the main IP's: 95.179.139.239 & 2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62
Change DNS template to hardcoded entries, instead of placeholders:
<domain>. MX <domain>.
<domain>. A 95.179.136.198
<domain>. AAAA 2a05:f480:1400:2cf8:5400:4ff:fe9a:198
Create a new domain (v39.confidential.cloud) with the IP's: 95.179.136.198 & 2a05:f480:1400:2cf8:5400:4ff:fe9a:198

ACTUAL RESULT
v39.confidential.cloud. A 95.179.139.239
v39.confidential.cloud. AAAA 2a05:f480:1400:2cf8:5400:4ff:fe9a:bb62

EXPECTED RESULT
v39.confidential.cloud. A 95.179.136.198
v39.confidential.cloud. AAAA 2a05:f480:1400:2cf8:5400:4ff:fe9a:198

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug.

SUPPORT ACTIONS OF INVESTIGATION / RESOLVING

POSSIBLE TEMPORARY WORKAROUND
1. possibility) avoid different mail sender IP's and domain IP's
2. possibility) correct the DNS settings by hand after domain creation.

LOGS AND ANY ADDITIONAL INFORMATION
 
It's been confirmed as a product issue. It will be fixed in a future update. Internal tracking ID: PPPM-14175
 
You must log in or register to reply here.

Similar threads

K
Forwarded to devs Custom domain name configured for autodiscovery not used for iOS QR code
Replies
2
Views
367
Peter Debik
P
Fabian H
Question Best practice email setup
Replies
4
Views
462
Kaspar
K
B
Issue Assistance Required: Correct DNS Settings for Mail Servers in Plesk
Replies
0
Views
415
BHK
B
f0rtem
Question Unable to use SSL unless I expose my IP?
Replies
2
Views
788
f0rtem
f0rtem
F
Issue Plesk Migrator post-migration check: "The domain does not have a mail service IP address."
Replies
0
Views
610
fliegerhermi
F
Back
Top