ok, this is probably going to sound a bit daft but:

what do all you enom people use for you clients?

the enom api seems a bit basic to register domains and so on.

is there some enom software out there i have missed?

or do you all program your own interfaces?

You can use their "canned" system which I believe is called registry rocket or you have to code your own. There are examples of php/perl and asp available. I'm working on my site in PHP.

Frank

yeah, i got the php api, and as i say it seems really basic. i can't believe everyone just writes their own.

eNom has something very interesting coming down the pike in the next... oh, let's say... one to four weeks, or thereabouts. It will directly address the subject of this thread. And I think, from what I've heard, that most with the types of concerns expressed here will be pleased.





Quite literally as I was typing the above words, it seems eNom updated its web site with some information about the very thing I just wrote about. I wasn't aware eNom was going to announce it before actually being able to offer it. But I'm glad it has. Check out details about their new, upcoming offering at:

http://www.enom.com/help/faq_pdq.asp

i don't get how that is different from the registry rocket service :confused:

Originally posted by thebyp2
i don't get how that is different from the registry rocket service :confused:

Registry Rocket is extremely limited. One color (tan). One, not-terribly-customizable look and feel (http://www.domainlightning.com/regmaint.html). Other than the logo, you can control almost no other aspects of Registry Rocket except:

- The prices charged
- The page to which one exits when one clicks on the "Exit" link
- Whether or not special features like "Name My Phone" appear in the control panel

That's pretty much it.

While Registry Rocket is completely functional for what it does, and while many eNom resellers will continue to use and be happy with it even after PDQ goes live, there's simply a bunch of stuff Registry Rocket doesn't do and that the new PDQ will do!

For example, Registry Rocket won't let one register a list. It has no "eNomitron" (name spinner) capability. It has no ability to register, configure or control the 10-page free web site that comes with all eNom domain registrations. It has no ability to globally edit domain records. One cannot control a parked domain's parking text from the Registry Rocket interface. One cannot set the auto-renew options using Registry Rocket... or "push" a domain to another eNom account. And through Registry Rocket, an owner of several eNom domains cannot do what eNom calls "domain portfolio management." Just to name a few.

eNom offers a ton of features that many people don't know about or haven't used because their only eNom experience has been either via a reseller's Registry Rocket interface, or the generic, tan access.enom.com (http://access.enom.com) interface. Up to now, the only way for one to get complete control of all features that eNom offered with every domain has been for one to have an actual log-in ID directly on the eNom.com web site (https://www.enom.com/Login.asp). So the way many resellers have been giving "power users" all of eNom's features has been for the reseller to create retail sub-accounts for the retail end users so they could actually log-in on the eNom.com web site (https://www.enom.com/Login.asp). A retail sub-account on the eNom.com web site (https://www.enom.com/Login.asp) behaves exactly like an eNom account that anyone can get directly from eNom by going to eNom's web site and just signing-up (https://www.enom.com/NewAccount.asp)...

...the salient difference being that the retail sub-account that an eNom reseller can create on the eNom.com web site (https://www.enom.com/Login.asp) will usually offer the reseller's retail customers somewhat lower retail pricing than eNom offers retail customers who sign-up directly on its site (https://www.enom.com/NewAccount.asp).

eNom's new PDQ interface (https://www.enom.com/help/faq_pdq.asp) allows the reseller to offer its customers a web site wherein the reseller's customers can register a domain name and then control all (or at least most) of the things that they cannot now control using the Registry Rocket interface. And the reseller can do so with the reseller's brand (and not eNom's) clearly in front of the customer's eyes. Through such a site, the retail, end-user, domain registrant customer can have pretty much the same degree of control over pretty much all of eNom's features as they would have if they had a reseller-provided log-in ID right on the eNom.com web site (https://www.enom.com/Login.asp).

I don't mean to sound like one of eNom's PR people, here -- and I don't work for eNom or anything like that -- but I have to say that if PDQ will do everything it seems it's going to be able to do, and if it's not buggy and problematic for a long time after it goes live (which I've heard could be sooner than originally thought), this will become just about the most powerful and full-featured domain name reseller tool on the Internet... far outpacing almost any other reseller-hosted API or registrar-hosted reseller interface.

The only stumbling point for some will be PDQ's pricetag. The Registry Rocket interface is currently (and as I understand it, will remain) free to all eNom resellers. The new PDQ interface will cost an eNom reseller $99 per year.

So now what d'ya think?