• 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.

Nameserver DNS entrys for subdomains are set wrong when plesk is primary DNS

Polli

Basic Pleskian
Username:

TITLE

Nameserver DNS entrys for subdomains are set wrong when plesk is primary DNS

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.66#1 Web Pro on Debian 12

PROBLEM DESCRIPTION

NS-entrys are made "wrong" by Plesk when Plesk is primary DNS. My registrar has correct GLUE-records and domains are resolved correct. The subdomain got "wrong" NS-entrys e.g ns1.mta-sts.boldorboard.com wich should be ns1.boldorboard.com for the subdomain mta-sts.boldorboard.com

STEPS TO REPRODUCE

I made Plesk the primary DNS and set GLUE-records at my registrar (INWX). Plesk has the following entrys for example.

boldorboard.com A 62.138.14.246
boldorboard.de A 62.138.14.246

My Server has a second IP wich I use for the second NS entry. I know that this is not the right way to set a Nameserver. But for now it is OK for me and I live with the risk to have my sites not reachable.

Plesk DNS entrys are as follows.

boldorboard.com A 62.138.14.246

ns1.boldorboard.com A 62.138.14.246
ns2.boldorboard.com A 188.138.25.3

I add a subdomain for an mta-sts entry

mta-sts.boldorboard.com A 62.138.14.246

Plesk now sets the NS to the following entrys for example.

ns1.mta-sts.boldorboard.com
ns2.mta-sts.boldorboard.com

This config is working but the record is not resolving to an IP

ACTUAL RESULT

My Log shows this error for example

Code:
/opt/psa/admin/bin/checkdns 'mta-sts.boldorboard.com' 'ns2.mta-sts.boldorboard.com.' '62.138.14.246' failed with message: *** Error  : Unable to resolve the nameserver 'ns2.mta-sts.boldorboard.com.'. Please set correct nameserver

The domain and the subdomain is working and I can reach files on it via https without any errors.

mxtoolbox shows DNS lookup is fine. DNS check failed with "no results found"

When I set the correct NS-entry, it shows me a warning.

boldor_08.png

With these entrys the record is valid and no entrys are in my log, but Plesk will revert these settings with next DNS zone update.

Please see following Images for more details of my current settings and testing:

boldor_01.png

boldor_02.png

boldor_03.png

boldor_04.png

boldor_05.png
boldor_06.png

boldor_07.png


EXPECTED RESULT

For my opinion the NS record must be:

ns1.boldorboard.com instead of ns1.mta-sts.boldorboard.com
ns2.boldorboard.com instead of ns2.mta-sts.boldorboard.com

I both cases mxtoolbox shows "no results found" but I dont get errors in my log from the "wrong" entry.

ANY ADDITIONAL INFORMATION

If this is a normal behaviour from Plesk, please let me know. But this is strange.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
This does not seem like a bug to me but by design because of the default template. Besides, you wouldn't be editing the DNS at the subdomain level to begin with but at the main domain level meaning that you will never hit that sub sub domain to begin with (unless you add a new DNS entry manually for it in the main domain).
 
Thank you for the report, @Polli. However, as mentioned by @scsa20 this is indeed not a bug, but due to DNS template. I am assuming that you are using the default template where the NS value is ns1.<domain>., which essentially replaces <domain>. with the corresponding domain/subdomain. If you would like to avoid that, you might replace the NS values in the DNS zone template with the actual domain, e.g. boldorboard.com. That will then be applied to all domains/subdomains.
 
Back
Top