This is another example of where pre/pst DNS add, DNS modifies, and DNS delete hooks could be beneficial.
Assuming that the server administrator has a way to automatically pass DNS changes to these providers - then all they would have to do is code something specific for that DNS provider whenever SPanel does a DNS add, DNS modify, or DNS delete.
I don't know if it's SPanel's responsibility to write specific code to link to a dnsimple, route 53, dnsmadeeasy, or whatever 3rd party DNS provider might be popular at any given time. But if SPanel provided these pre/post DNS Add, DNS Modify, and DNS delete event hooks, then individuals could code this at their leisure.
Hi Scott. We'll develop anything that is useful for people in SPanel. It's all about demand and priorities -- logically, we'll firstly work on the features with most demand.
Is there value in that pre and post hooks like this could alleviate a lot of these feature requests? Or at the very least open the door for administrators to apply their own fixes instead of waiting for SPanel to write code to incorporate these changes?
Sometimes a linear view of feature requests may not be the best route. Instead of solving feature requests one by one, it could be that one feature request - if implemented - solves several of the other feature requests ahead of it.
Comments (4)
Just to mention that SPanel got an integration with Cloudflare.
This is another example of where pre/pst DNS add, DNS modifies, and DNS delete hooks could be beneficial.
Assuming that the server administrator has a way to automatically pass DNS changes to these providers - then all they would have to do is code something specific for that DNS provider whenever SPanel does a DNS add, DNS modify, or DNS delete.
I don't know if it's SPanel's responsibility to write specific code to link to a dnsimple, route 53, dnsmadeeasy, or whatever 3rd party DNS provider might be popular at any given time. But if SPanel provided these pre/post DNS Add, DNS Modify, and DNS delete event hooks, then individuals could code this at their leisure.
Hi Scott. We'll develop anything that is useful for people in SPanel. It's all about demand and priorities -- logically, we'll firstly work on the features with most demand.
Is there value in that pre and post hooks like this could alleviate a lot of these feature requests? Or at the very least open the door for administrators to apply their own fixes instead of waiting for SPanel to write code to incorporate these changes?
Sometimes a linear view of feature requests may not be the best route. Instead of solving feature requests one by one, it could be that one feature request - if implemented - solves several of the other feature requests ahead of it.
Replies have been locked on this page!