Nameserver ip assignment for reseller is seriously flawed!

[pucky]

I dont think much thought was put into this.

Why on earth, does any reseller have the ability to click on NAMESERVERS unless they have be given nameserver ability? So they are resellers, is that the reason to give them the nameserver option on their menus? Is that also the reason to give them IP MANAGEMENT so they can see the number of users on the entire system? (Posted in another thread and still waiting for a reply).

Why does the reseller have the ability to click on the CREATE button to create two nameservers in their domain name? Should not be allowed.

So that means, any reseller can click on Nameservers and create two nameservers in their domain name then they can turn around and register the ip of the server, and the ip of the our secondard nameserver, and have FREE nameservers on their account without paying for nameservers. Many hosts charge extra for this feature including us.

Second, what is the difference between assigning two ip for nameserver to a reseller as opposed to not assigning any THEM registering the main ip of the server as ns1 and our ip for ns2? There is no difference. If reseller were restricted from entering the Nameserver option, then they would not be able to CREATE nameservers for their domains.

Next, WHY IS THAT DA does not allow the main servers ip to be assigned as NS1? Give me break! This is standard practice in all control panels these days, Plesk, cPanel, Ensim to name a few. if i wanted too, i should be able to assign ns1 as the servers main ip and ns2 using an additional ip from the pool. Since DA allows shared hosting to happen anyway, i dont see the reason why NS1 cannot be the ip of the server and NS2 the ip from the pool. I'm talking about the assignment of nameserver FOR RESELLER not for us. There is a difference. DA does not allow us to assigned the servers ip as one of the ips for the reseller.

This would mean we save an extra ip as opposed to wasting 1 by not allowing us to use the ip of the server.

Likewise, i should be able to assign any reseller to NS1 server ip and give them a second ip from the pool. I should not have to create 2 new ips for this.

This is called WASTING IP's. ICANN would be very upset about that!

So then i ask this question for the upteen time. HOW DO I MODIFY THE THEME TO RESTRICT PEOPLE FROM CLICKING ON OPTIONS I DONT WANT THEM TO CLICK ON?

 

[redesb]

Hi pucky,

I do not know the answers to most of your questions, perhaps is better than you send one email to DA support.

Although I believe that I can respond to one quite easy:

HOW DO I MODIFY THE THEME TO RESTRICT PEOPLE FROM CLICKING ON OPTIONS I DONT WANT THEM TO CLICK ON?

SSH access to the server, cd to 'usr/local/directadmin/data/skins' and copy the 'enhanced' skin dir to a new one like 'my_enhanced', cd to 'my_enhanced/reseller' and edit the file 'content_main.html' comenting or deleting the line who says:

<a href="/CMD_NAME_SERVER">|LANG_NAMESERVERS|</a><br>

thats all! Of course you can modify the original one but when you update DA your changes will be lost.

You only need to assing the new skin to your users.

Hope this help,
Regards

 

[pucky]

Alright, that is possible however doesnt the admin loose the ability to use the nameserver option in that case? And that means the reseller could also select my_enhanced as opposed to enhanced.

 

[redesb]

No, the admin don't lose anything because his files are located in the 'admin' dir and you don't touch her files.

You can set the reseller skin in the reseller package you assing him.

I forget to say, to do a 'chown -R directadmin.directadmin ./my_enhanced'

 

[sullise]

BTW, removing the link from the skin does NOT disable the function. If they know url, they can simply type it in and get access to that function. Though removing it will discourage those without that knowledge.

 

[Remco00]

You can also remove the corresponding CMD line in reseller.conf which is in the root dir of your skin. This way the function is completely disabled.

 

[sullise]

True (and it's files_reseller.conf btw), but that would disable it for ALL resellers, including the admin reseller account, not just his resellers.

 

[pucky]

True (and it's files_reseller.conf btw), but that would disable it for ALL resellers, including the admin reseller account, not just his resellers.

It disables it for Admin as well. Cant do that! What is the solution besides messing with themes?

 

[sullise]

Not sure, but if you disable DNS ability via the reseller setup, it might disable the Nameservers function...else not sure what else you can do.

 

[pucky]

The proper fix for this is to have the ability to turn off EVERY option from all user and resellers at the admin level. Thats the truth to the matter. That way, you dont have lingering options that cannot be disabled.