Drams Experiences

[navpros]

Hi Folks,

As some of you may know, I have made the leap into official ETP status with Enom.com. I already have a handful of active resellers and doing quite well in the domain brokering side of the business, but now ready to focus on long-term reseller strategy.

I will be flying out to Jackson, MS later this week to discuss options with a group of developers for the all new dandydomain.com website. What I am in need of is some feedback pertaining to your overall experiences with DRAMS.

It seems to be a great fit but I am bit concerned as to how advanced it is and if it is "bug free" or not. If any of you have used/tested DRAMS I would love to hear from you.

Thanks in advance.

Note to forum members: lsutiger was formerly "dandydomain". Just wanted to make certain everyone is aware of the name change over time. Thanks, GSW.

 

[eSology]

Howdy fellow ETP. I bought DRAMS, Whois.cart, and PDQ. After thoroughly testing all of them I am sticking with whois.cart and PDQ. First priority to PDQ because I believe that domain owners should have full rights. With DRAMS and whois.cart the domains reside in your eNom account which means that they cannot push domains when they want to. There are more reasons but this is my biggest issue. Second I guess would be the updates/bugs.

 

[navpros]

Thanks for the feedback acts. I had no idea that domainers could not do a "push" through drams. That is definately a BIG issue. Depending upon what we can come up with in Jackson this weekend, I may use the PDQ as a temp fix. If it works quite well, then perhaps long-term possibility with PDQ. Anyway, sending you a pm to ask you a little something regarding PDQ.

Many thanks!

 

[eSology]

Whois.cart is the same. The domains are dumped in the eNom account you use for the connection between the API and eNom. To me this was unacceptable. Over at WHT people are complaining about eNom resellers preventing transfers, changing whois, etc, etc. I always look at the site people are complaining about and 90% of the time it is a DRAMS implementation.

 

[navpros]

Very interesting to know. Thanks again for the feedback. PM sent.

 

[eSology]

I can't believe I'm giving you feedback. I'm an OU Grad!

 

[navpros]

Originally posted by acts837
I can't believe I'm giving you feedback. I'm an OU Grad!

LMAO. Looking for some payback? Go tigah's!

 

[RJ]

Originally posted by acts837
Whois.cart is the same. The domains are dumped in the eNom account you use for the connection between the API and eNom. To me this was unacceptable. Over at WHT people are complaining about eNom resellers preventing transfers, changing whois, etc, etc. I always look at the site people are complaining about and 90% of the time it is a DRAMS implementation.

This will be true for any solution that uses eNom's API. For instance RegisterFly and NameCheap both are eNom resellers using custom API solutions. You are only able to push into other accounts at the same reseller and not into an actual eNom account.

 

[navpros]

Originally posted by -RJ-
This will be true for any solution that uses eNom's API. For instance RegisterFly and NameCheap both are eNom resellers using custom API solutions. You are only able to push into other accounts at the same reseller and not into an actual eNom account.

Ahh! Thanks RJ. I am currently using the PDQ which I find to be a perfect solution. Now that you have the ability to customize almost the entire home page, it makes it even better.

 

[Peter]

drams can be fully customised as well.

regarding not being able to push domains this as RJ says would be true for any enom api based product / service but to be honest I think that is the way it should be, if you get a customer that likes fiddling with things and might try it to see what it does and if they pushed it you are copletely unable to help which of course reflects bad on you as, as far as the customer is concerned you have responsibility over their domains / hosting etc

 

[theparrot]

Is there anyone who has drams that would be willing to let me take a look at it? I want to see how hard it would be to use another registar with it, or share the use of its db structure with custom code.

Even a dump of the database table structure would be helpful.

 

[QBert]

sorry for the offtopic post but whats the site for PDQ, i would realy like to have a look at it.

Thanks

QBert

 

[eSology]

http://www.registerpdq.com/ <- eNom's functional example of PDQ site

 

[Peter]

Originally posted by theparrot
Is there anyone who has drams that would be willing to let me take a look at it? I want to see how hard it would be to use another registar with it, or share the use of its db structure with custom code.

Even a dump of the database table structure would be helpful.

no other registrars are supported yet but they are working at supporting OpenSRS.

The code is unadaptable as it is encoded (1 version with zend and anther with Ioncube) so you would not be able to add the functionality yorself.

 

[theparrot]

well, if i had a dump of the db structure I would write code to import it into my own code to replace it for another registar was my thought.

 

[brainstorm]

Interesting thread...

 

[Peter]

Originally posted by theparrot
well, if i had a dump of the db structure I would write code to import it into my own code to replace it for another registar was my thought.

to be honest I think it is too based around the enom api for that, I think it would get to the stage where you would be just as well to completely write your own solution.

 

[navpros]

Well, I went with the PDQ and from what I can tell this seems to be the most cost effective, user-friendly, way to go. Of course, there are advantages and disadvantages. What has impressed me the most is that the PDQ sites are alot more customizable now, than what they used to be. If you visit http://www.dandydomain.com you'll notice that I have setup a link exchange on the home page, some affiliate links, etc. At one time, you were very limited and only had one small section that was customizable. I transferred all of my domain name customers from my WWD account over to the new PDQ site at no cost to them and already generating a nice steady income from a couple of ISP'S. IMHO - I am very fond of the idea of developing a site from the ground-up using the API, but the PDQ serves its purpose for either a temp or long-term solution.

 

[Raf]

I myself have used Whois.Cart() and definately recommend it, however I believe that there v3. release will be better. As for using DRAMS, it's not that bad really. I don't know really if its bug-free or not.