Welcome to WebmasterWorld Guest from 188.8.131.52
The problem is that their authentication keys are completely useless and I cannot gain access to my account to unlock the domain. To be sure that the problem was not with my computer, I even requested several authentication keys and asked my friend to try unlocking it from his computer. That failed as well, proving that it is a glitch due to the registrar.
Emails to the registrar at domain@d******e.com and tech@d******e.com both go unanswered, even if marked high priority. Phone calls overseas get answered by a machine and then the calls get disconnected after 2 minutes. Pool support says that this issue does not concern them and that I need to take it up with the registrar, which is ICANN accredited.
At this point, I've already wasted several hours attempting to unlock this domain. Can someone please shed some light on unlocking this domain?
note: Due to forum rules about name dropping, the name of the registrar has been masked. If you need the name of the registrar, please PM me.
You might also try sending an email to ICANN registering your complaint about the registrar AND Pool. CC Pool and the Korean Registrar.
Next, try the fax. Sometimes a fax gets people's attention. My letters are faxed on my law firm letterhead. That helps. Got a friend who's a lawyer? Do him/her a favor and ask for one in return. Most lawyers will cut lose a single letter in return for a favor. Also, when I have to go so far as faxing a letter the fax is concise: "I'm trying to be nice but I'm frustrated because I've tried x, y and z. I am a lawyer and if I have to I'll travel to your country and sue you for fraud, the domain transfer and my expenses, plus report you to the local authorities and ICANN." (Only sent such a letter once. Domain released. I would have traveled if need be. They could tell. ;0).
Next, find a friend who speaks Korean. I would not be surprised if a member here offered to help. Perhaps post in the community forum.
You could always send money. Send them $20 in an envelope with a short letter, simple words. Money sometimes talks louder than words. I did this once. They called me because they couldn't understand why I sent them money. They fixed the problem. They were innocent, really. I told them to keep the money. I guess that would have happened anyway.
I've pretty much used every trick in the book as needed. Don't want to jinx myself by saying my batting score.
I had a domain stranded in Korea once (similar issues, but mostly language barriers). I just sent a polite, short, easy to understand email every two days or so. After a week someone replied using very poor english. My worries were in vain - they were good people that just didn't have a clue what I was saying in my emails. It took a week or so, but they finally released the domain.
People are people. Unlocking a domain for the registrar is a simple thing to do, but someone has to do it. How often do we put off easy tasks because they seem a pain to deal with? And if your honest your just not concerned that the domain owner is freeking out thinking your somehow planning on stealing the name.
Also, don't forget having the pleasure of bidding against yourself in the silent auction.
Remember that ALL Pool grabs go into silent auction even if there are no bidders against you.
Also, be careful about Pool's "sale" of .pw domain names. .PW is not a traditional domain that can host a web page, forward traffic or even sell.
And, since Pool is not even a good name grabber anymore, I only use them when I want to get a name that is worth $300 or more to me.
Anyway, use GoDaddy transfer concierge and they should help you.
Thanks to all who responded.
joined:Mar 9, 2005
any of the registrars that offer backorders do this as that is what backordering is-
what i like about pool.com is that they have an auciton of expiring domains that you can aquire for small amounts -if you do the research yourselff you can get a good buy.
Though i have had registrar problems similar to those mentioned above
[edited by: engine at 2:41 pm (utc) on Mar. 9, 2005]
[edit reason] TOS [/edit]