• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question DNS zones for subdomain vs. domain

dirk_s

New Pleskian
There are two ways to setup a subdomain with Plesk:
1) as a subdomain (SUB) of a TLD
2) as a separate "domain" (SUB.TLD) in addition to the related TLD

Both have advantages and disadvantages... (e.g. possibility to make use of alias is only available to a domain plus others)
How can I setup DNS correctly in Case 2)? I run my vServer as primary DNS and my registrar as secondary DNS. In case of 1) the secondary DNS Servers are reported as authoritative. In case of 2) I need to setup an additional zone file for the SUB.TLD at my registrar - as the DNS zones are separated on my vServer - one for TLD and one for SUB.TLD. Otherwise the secondary DNS servers are not reported as authoritative.

Goal: I would like to have one DNS zone file for the TLD, including(!) the related SUB.TLD DOMAIN DNS records. Is there anyway to achieve that with Plesk? That SUB.TLD doesn't create its own zone file, but updates TLD zone file instead?

Thanks for your help.
 
Back
Top