search

FOSSBilling / FOSSBilling

Empower your hosting business with FOSSBilling, the free and open-source solution for efficient billing and client management.
https://fossbilling.org
Apache License 2.0
829 stars 182 forks source link

[Feature Request] DNS Management for domain #1152

Closed binsaryunus closed 1 year ago

binsaryunus commented 1 year ago

fossbilling should add future domain management dns for domain templete to change side client to redirect owned domain to other hosting Untitled image (3)

John-S4 commented 1 year ago

Unless I'm missing something (and I'm tired so it is possible) I would think that this was outside of the scope of the billing platform and should be done with a server control panel.

@binsaryunus why is this something that you would want/need to do from within the billing system?

Anuril commented 1 year ago

I also don't think that this should be in fossbilling. Adding DNS Management to any platform is.. a lot of work...

Imo either use a server control panel like hestia or in the future maybe a specific DNS hosting manager might be added as a plugin. (F.eX https://atomiadns.com/ or https://www.poweradmin.org/

John-S4 commented 1 year ago

I will leave this open for a couple of days to see if the OP has some reason for this being in FOSSBilling that I'm missing but if not then I am going to go ahead and close the issue.

tobsowo commented 1 year ago

I think it will be nice to have in FOSSBiling so that not every task will need logging to the web panel Egbe it can be quickly done in the billing.

jaapmarcus commented 1 year ago

It can be done from within Fossbilling but the question is should this be part of the Current Domain module and my answer is a clear no.

Off course it can be part of a certain module that needs to be developed but the question then is on what system it is going to be build.

But I don't think this should be the focus of Fossbilling team to decide it if a user want to build a certain function please go ahead...

BelleNottelling commented 1 year ago

Yeah I'm going to be completely honest. I can understand the appeal of this, but right now with the current number of maintainers we have, the amount of work that needs to be done, and the very significant number of open feature requests, I would consider this to be a very, very low priority. Assuming we even want to implement this ourselves which we likely wont.

binsaryunus commented 1 year ago

@John-S4 this future very helpful to management DNS from billing like whmcs have cpanel manage it plus point if fossbilling have this future like @tobsowo say this help side client quickly to set it.

John-S4 commented 1 year ago

In my mind a much better long term solution is to improve the integration with server control panels including SSO, so that FOSSBilling would have a link to go and manage the DNS in the server control panel.

Personally I think that there should be tight integration between billing/client-management systems, and server control panels, but there are clear lines for me about which things each one should do.

like whmcs have cpanel manage it

I haven't used WHMCS (or cPanel) for a long time, but that sounds like the DNS management is handled by cPanel rather than WHMCS, which would support my point?

tobsowo commented 1 year ago

Adding the WHMCS feature list for reference purpose image

jaapmarcus commented 1 year ago

WHMCS still depends on a 3rd party software like Cpanel to run the DNS servers.

If somebody want to create it please go ahead but for us it is currently not a priority..

BelleNottelling commented 1 year ago

People need to realize a couple of important things about FOSSBilling:

  1. We don't have many active contributors. Generally speaking, FOSSBilling will have 1 or 2 active contributors with temporary peaks up to 3. Right now, we are at 1 (me).
  2. We aren't paid for this. I haven't tracked it, but I estimate I've put in anywhere between 6 and 8 months of full-time development towards FOSSBilling. That's roughly $49,978.5 - $66,638 USD of completely free development from me alone.
  3. FOSSBilling is still considered pre-production software. There are parts of it that don't work right, system that are overly complicated or convoluted to use and maintain, and just some security features that are outright missing such as MFA support.

So implementing new features is currently a very low priority and if we are going to implement a new feature, it needs to be something that almost everyone using FOSSBilling will benefit from. Unfortunately, a handful of people finding something useful or the fact that WHMCS supports it is not enough of a reason to justify putting any priority towards something.

And that's before we even mention the fact that there's currently 90 other open feature requests (91 total).