Help With Organising DA Ip Structure

[wanener]

Hi Everybody

I'm new in DA
i installed DA on 1 Server and assign 1 IP To it

after that i followed the after installation guide and initial setup

i free up and added 3 more IP on same subnet

my question is How To Organize My 4 ip address ( 1 for Server - 1 Dedicated for 1 Reseller - 2 Other IP Share for All Resellers and users )

 

[SeLLeRoNe]

Is up to you, you should also use the server ip (the main one of directadmin installation) for everything unless you need an ssl cert or have a reseller that want to have his own ip.

Regards

 

[wanener]

Is up to you, you should also use the server ip (the main one of directadmin installation) for everything unless you need an ssl cert or have a reseller that want to have his own ip.

Regards

tanks for the reply
I know that its up to me !
but im Confused how to do that !

is there any way to don't use server ip for reseller or user and leave it free and just for main domain ?

if Not what is the procedure of assign 2 ip address as shared for the whole resellers and users ?

 

[SeLLeRoNe]

At admin level, go to ip management and assign the server ip to admin.
Than assign 1 or more ips to resellers you wanna them to be able to use.

That should be what you are trying, i suppose.

If i wrong understood what you meant, sorry.

Regards

 

[wanener]

At admin level, go to ip management and assign the server ip to admin.
Than assign 1 or more ips to resellers you wanna them to be able to use.

That should be what you are trying, i suppose.

If i wrong understood what you meant, sorry.

Regards

i tried to assign server Ip To Admin but nothing Happened ( without Error )
and when i assign 1 ip to reseller i cant assign it another one and returned and error !

i want to have 2 shared ip for all my resellers and shared for all user
and make my server ip just for one domain

i forget to mention that i already have 4 reseller and cant find the option that change the # of and assigned Ip to them

 

[SeLLeRoNe]

Ok, maybe you cant assign multiple reseller to a single ip (never tryed so my was more like a suggestion).

For server IP maybe you are right, everyone will be able to use, maybe can be made as Feature Request to disable other resellers from use server ip and another one for use single ip for multiple resellers.

Regards

 

[wanener]

Thanks for the Reply How Do you Manage This Situation ?
What is Your Suggestion ? assign 1 dedicated Ip For Each Reseller ?
i want to know how to manage Ip's
what are the steps !
to Assign 2 IP's for current resellers (1st The Server IP and The other Free IP )

 

[wanener]

Any Idea ???

 

[nobaloney]

It's really up to you. We don't charge for justified IP#s, so we don't give the reseller account it's own IP# either to share or keep exclusively, unless they request it.

Jeff

 

[wanener]

It's really up to you. We don't charge for justified IP#s, so we don't give the reseller account it's own IP# either to share or keep exclusively, unless they request it.

Jeff

I don't Understand what do you mean
but my problem is when i create a reseller with the shared server IP
my reseller need to have their own DNS like ns1.resellerdomain.com but there is no ip on their panel to create ns1 and ns 2 (they use Virtual Actually )
but after that wen i create a package and try to add a user with that package it return the error ( you must own an Ip address )

where is the problem ?

 

[nobaloney]

If I understand you correctly you simply create the reseller. Nothing special for IP#s or DNS. That will create the reseller using your two main nameservers.

Then you edit the reseller account, this example uses example.com as YOUR domain, where you've got YOUR nameservers already set up, and example.net as your reseller's nameservers.

In this scenario you'd set up these nameservers for your reseller:

ns1.example.com
ns2.example.com

by editing the reseller. This does not require any IP#s; it simply sets those nameservers as the default when DNS is later created for the reseller's users.

Then you or your reseller must add A records for the reseller's nameservers, in the zone file for example.net (reseller's domain):

ns1.example.net. (don't forget the dot) needs an A record pointing to the same IP# as ns1.example.com (your nameserver, already set up)

ns2.example.net. (don't forget the dot) needs an A record pointing to the same IP# as ns2.example.com (your nameserver, already set up)

Important you use A records, NOT CNAME records.

Then either you or your resellers (depending on who has control of the domain registration must set up the nameservers and their IP#s at the registrar where the domain is registered. This is not the same as pointing the domain to the nameservers, but rather sets up glue A records for the two nameservers in the nameservers hosting the TLD's top level (for example, the .com domains have A records for the nameservers in the *.gtld-servers.net nameservers (where * stands for the first 13 letters of the alphabet).

Once this is all set up properly you can test for it with:

dig ns1.example.net +trace

Then those nameservers will be assigned, and will be used for all newly set up users on the account, and will work.

To see a working example:

dig ns1.ns-one.net +trace

to see a nonworking example (nameservers aren't set):

dig ns1.nobaloney.net +trace

Jeff