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

Correct setup for Client/Reseller Accounts for DNS

J

jjsba

Guest
Hi there,

If I have a PLESK server and it is setup for me as hostingcompany.com, with my server DNS template looking like:

<domain>. NS ns1.hostingcompany.com
<domain>. NS ns2.hostingcompany.com
<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. A <ip>
mail.<domain>. A <ip>
smtp.<domain>. A <ip>
webmail.<domain>. A <ip>

When I setup CLIENT accounts, and that CLIENT goes to setup a domain under THEIR account, that DNS default setup is putting our hosting company default DNS servers ns1/ns2.hostingcompany.com in their client's DNS records.

Should I:

A) Take the two default NS records OUT of the server default DNS record and then instruct the CLIENT to add in his own NS records for each client each time he creates a domain?

B) Leave the two default hostingcompany.com NS records IN the server default DNS record and then instruct the CLIENT to remove them on each domain he creates and add in his own for each domain he creates?

C) Create a generic nameserver setup like ns1/ns2.genericnameserver.com and allow resellers to either use our generic nameservers or setup their own private ones?

D) Are NS records even required for each and every domain? Can I just leave them OUT of the default server DNS template and the domains that the CLIENT creates will be OK without the NS records?

I guess I was just wondering if there was a way for a CLIENT to create his OWN DNS TEMPLATE for HIS domains under HIS client account?

Any input will be appreciated.

Thanks!
 
Back
Top