- clients need to be able to put authorization code into form and transfer domain to their account with me.
WHMCS does this, I use resellerclub and it supports this feature. Maybe Enoms API doesn't support this feature.
- Able to register domain names without getting hosting, which then automatically displays a "coming soon" message when the domain is viewed.
WHMCS will let you sell domains without hosting, look on the order page, it has a domain only option. In terms of a default page, the customer will input their name servers upon registration so is there any need to try setting this function up. If you did you could use your own name servers and set up a vhost to show a 'coming soon' page.
- Able to login to their account, and point their domain at whatever nameservers they want.
WHMCS allows name server modification, at least with ResellerClub, I'd have to guess that Enom's API and hence WHMCS's Enoms module supports this.
What are "default host records" and how do I set them up?
I guess you're referring to vhosts within the httpd servers configuration file. You'd set a vhost with the domain as the wildcard symbol i.e. * so that any domains not configured on the server show a 'coming soon' page.
What if somebody registers a domain but doesn't get hosting. Then, later, they get hosting for the domain, do they need to update the namerservers that the domain is pointed at?
This would be done via WHMCS either by the customer or the admin.
Thanks for the reply. My brain kinda hurts right now . I want to address just one part of this whole situation, before trying to understand other parts.
When someone goes to your website, and registers a domain, what default nameservers is it registered to? Currently my website uses my own custom nameservers as default for new domain registrations. The Enom API requires domains to be registered to their nameservers in order to allow my customers DNS Management functionality. This seems problematic, as lets say someone registers a domain which is automatically pointed to the Enom nameservers, but then they try to addon the domain to their hosting account, the domain will be pointed to the wrong nameservers. Basically, it seems like I have to choose between the ability to offer DNS management my customers, or having newly registered domains pointing towards my company's nameservers.