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

Bug found: DNS NS Record on Domain-Aliases without Customer account

C

caomhan

Guest
Hey Guys,

i've found a bug in my Plesk 10.1.1 installation.

Plesk 10.1.1
Debian 5.0, x64

In my DNS-Template-Settings i've created a NS Record like this:

<domain>. NS srv01.fixedDomain.com.

In the value there is no variable as you can see.
Plesk should set this NS Record as shown above to all domains and domain aliases.

Plesk do the job right on every customers domains and domain aliases.

Now the Bug:

But if you have an own subscription without a customer account then Plesk sets the NS Record like this:

Main Domain: example.org. NS srv01.fixedDomain.com. <- that's right
Domain Aliases: example2.org. NS srv01.example2.org. <- that's wrong!

The domain alias NS Record get handled like a variable Record.
As i said above: Only on subscriptions without customer account.

I've check that on another server: Yes, same bug!

Please give me a feedback about this.

Cheers,
caom
 
Last edited by a moderator:
Hey again,

sorry, i've found something more about this bug.
It's not like i said above.

Here the real issue:

I have a domain configured inside Plesk named "exmaple.org" in a subscription.
The subdomain "ns.example.org" should be used as nameserver domain, so i configured this in the DNS Template settings e.g. like this:

<domain>. NS ns.example.org.

Domain aliases of this domain (the same as configured in the DNS template) gets the DNS record "ns.aliasDomainOfExample.org" instead of "ns.exmaple.org". The "example.org" will be replaced with the domain name of the domain alias.

This issue only exists if the domain name in a subscription is the same as defined in the DNS template settings for NS record, then the domain aliases of this subscription get wrong NS records.

Can anybody confirm this?

Please check this again.

Cheers and thanks,
caom
 
Back
Top