H-Shpere Reseller, PHP Configuration, Enom

Portal Home > Knowledgebase > Articles Database > H-Shpere Reseller, PHP Configuration, Enom

Posted by MetaSkinny, 12-07-2004, 12:11 PM
I have a H-Sphere reseller package with an unnamed hosting company. I've been trying to implement reselling domain name registrations using the Enom EPT API program. Unfortunately, I've run into an issue. My reseller account is setup on a Windows 2000 server with PHP support. The default PHP configuration does not meet the requirements of the Enom API. Required PHP Configuration: session.auto_start On session.bug_compat_42 Off session.bug_compat_warn Off My PHP Configuration: session.auto_start Off session.bug_compat_42 On session.bug_compat_warn On I contacted my hosting company and requested them to change these setting in the php.ini file. Because my account is on a shared server they will not make the change. They suggested I switch to their dedicated server solution. What problems could possibly arise from changing these settings? My hosting company has been top-notch since I signed on 4 months ago, but maybe it's time to move on? Or, maybe this is standard practice and I should forget trying to sell domain names? Thanks
Posted by IHSL, 12-07-2004, 01:50 PM
With Windows, changing php.ini can very quickly ripple problems through the server - I would imagine that's why they won't make the change. You could ask them to integrate enom into the CP - that takes around 1-2 minutes to do, and integrates the entire thing for you. You'd actually have no work to do, other than telling H-Sphere how much you'd like to charge each customer for the domains. Simon
Posted by MetaSkinny, 12-07-2004, 02:50 PM
Thanks for the response, IHSL. Enom is currently configured in my H-Sphere reseller plan, and I can offer domain registration to current hosting customers. My reseller hosting company has recently set their .com registration fee at $17.95; a five dollar increase from last month. Network Solutions, here we come! As you may be well aware of, H-Sphere does not offer a robust domain registration/management system. It's the biggest drawback to an otherwise great program; and it's a MAJOR drawback. It's weak and made even more so by the fact that each domain registration eats up a license. OUCH! I didn't realize I was this frustrated. Simply put, I want to expand my business offerings and H-Sphere is holding me back. SWF seeks scalable multi-server web hosting control freak. Must have a sophisticated automated billing and account provisioning system. A robust domain registration and management system is a must.
Posted by IHSL, 12-07-2004, 03:00 PM
Here's a tip for H-Sphere: Register the domain through an already active account - this will then bypass the need for an extra license That price is indeed expensive - not much I can comment on that, as it's more than double the enom price. You should be able to manage those domains will the utmost of ease. Another tip: Create a cname for your service domain, like this: The cname should be for "access.yourservicedomain.com" - and the domain it points to is: access.enom.com Now, type in access.yourservicedomain.com - login with the H-Sphere password, and you have access to the full enom management section When a domain is registered through H-Sphere, what most H-Sphere providers don't yet know, is that it also applies an enom management password to the domain, matching the one the user signed up with. That will give you complete control, and all at a domain that has your name in it. A lot of providers don't even realise they have this tool at their disposal Simon
Posted by MetaSkinny, 12-07-2004, 03:45 PM
Ah! Thanks for the info, IHSL. I didn't know that a domain name registered through H-Sphere sets up an Enom account with full domain management access. How about OpenSRS? It seems to me the best solution would be to setup a hosting account on my Linux server where the default PHP settings support the Enom PHP API. I could then use cname to direct my domain customers from mycompany.com to domain.mycompany.com. The downside to this workaround is that my Enom customers will not have access to my H-Sphere hosting features and my H-Sphere customers will not have access to my Enom features. It could get very confusing for some; especially when they register a new domain name in H-Sphere and are charged double of what my Enom customer pays. Then there is the customer who first registers a domain name then decides he's ready for hosting. That poor guy gets two bills from me, has to log into one account to manage his domain, then has to log in to another account to manage his hosting. That can't be good for business. I'm sure there is another downside lurking around the corner. Third party solutions = third party nightmares. I can feel it in my bones. Any ideas or experiences to relate?

Add to Favourites Print this Article