• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Different Name servers for my resellers

C

ChipMonk

Guest
I am a bit confused.

A, B, C are my resellers.


they have registered domains, a.com, b.com and c.com

192.168.224.001 is the ip for A
192.168.224.002 is the ip for B
192.168.224.003 is the ip for C

As they register domains through me, i register their name servers as follows:

ns1.a.com and ns2.a.com are set for 192.168.224.001
ns1.b.com and ns2.b.com are set for 192.168.224.002
ns1.c.com and ns2.c.com are set for 192.168.224.003

now its obvious that they will set those name servers to their respective ns systerms.

Is this thing possible?

if yes, how? what extra settings i might have to do? (other then giving them permissions for DNS management)
 
Chipmunk,

I’m going to take a stab at this:

You said that:

A, B, C are my resellers.

And

they have registered domains, a.com, b.com and c.com

192.168.224.001 is the ip for A
192.168.224.002 is the ip for B
192.168.224.003 is the ip for C

As they register domains through me, i register their name servers as follows:

ns1.a.com are set for 192.168.224.001
ns1.b.com are set for 192.168.224.002
ns1.c.com are set for 192.168.224.003

BUT, you did not mention their ns2. Records? They should be something (using your example that is) like this:

Ns2.a.com are set for 192.168.224.004
Ns2.b.com are set for 192.168.224.005
Ns2.c.com are set for 192.168.224.006

AND all of these IPs would point to your server by the collocation facility and added to your Plesk Control under Server Management.


At this point, your box is running one name server system isn’t it and wouldn’t it be unnecessary to have the resellers touch your dns at all? Also, when you add or added a.com and b.com you would have selected a static IP as opposed to using the shared or one of the shared IP s in the list.



Someone help me here because I’m talking out of the side of my head here and hoping to learn something from this…



HMIBarryLSalter –
 
bro, two suggesions :s

first, if u dont know a thing, dont help anyone based on incomplete information.

second, read the post properly before replying.
 
Back
Top