Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS Record Management within Registrar Extensions #2050

Open
adamh2021 opened this issue Jan 6, 2024 · 8 comments
Open

DNS Record Management within Registrar Extensions #2050

adamh2021 opened this issue Jan 6, 2024 · 8 comments

Comments

@adamh2021
Copy link

I'm not sure who manages the domain registry extensions but it would be nice to include another commonly used feature - DNS management.

I cannot say that all domain registry providers allow this, but I know that ResellerClub do - this was a well used feature back in the days when I was using WHMCS.

Maybe this could be included on the 'Manage' section as another tab called 'DNS Records' for example

2024-01-06 21_09_21-Domain registration
@getpinga
Copy link

If someone has an idea how is best to add it, I can work on it. Just I tried to add another product type / hosting, DNS, etc, but I had to change too many files in the core for it to work.

@adamh2021
Copy link
Author

@getpinga
I'm not sure it's even worth investing any time on this feature request at the moment. I've discovered other issues with the resellerclub extension - it does not seem to work well at the moment. See #2096

@BelleNottelling
Copy link
Member

If someone has an idea how is best to add it, I can work on it. Just I tried to add another product type / hosting, DNS, etc, but I had to change too many files in the core for it to work.

I am assuming you tried to base it off of one of the already built-in product types? They are still utilizing an service management setup that BoxBilling marked at deprecated and then continued to internally rely on indefinitely. I have it on my eventual TODO list to migrate these to the system that a 3rd party product would be using, but it's a relatively low priority. The TLDR is that any product type included inside of FOSSBilling except the API key product type is using this system and has been hard coded into a few sections of the back-end and a new one cloning this behavior and not being added will produce errors. I know, it's great.

So long as you use the non-deprecated functionality a new product type can be added to FOSSBilling without making any modifications. I did exactly that when I added in the API key product type via PR #1272. The only two file changes outside of it's own folder were to make our spellcheck pass because it was added to the main repo and I created a DB model for that's actually not even in use presently and is not needed.

@getpinga
Copy link

This is now available at https://github.com/getnamingo/fossbilling-dns

@adamh2021
Copy link
Author

This is now available at https://github.com/getnamingo/fossbilling-dns

This links with resellerclub DNS?

@jaapmarcus
Copy link
Member

This is now available at https://github.com/getnamingo/fossbilling-dns

This links with resellerclub DNS?

No

Supported options:
https://github.com/getnamingo/fossbilling-dns/tree/main/Servicedns/Providers

@adamh2021
Copy link
Author

Not as per the original ask.

Nice to know its available though.

@getpinga
Copy link

Not as per the original ask.

Nice to know its available though.

Sorry, actually misunderstood the original question. But anyway on my todo list is to link the dns and registrar module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants