Inside ICANNWatch  
Submit Story
Lost Password
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)

    Registrars Domain name transfer snafus
    posted by michael on Tuesday December 18 2001, @02:37AM

    Deb writes "After having just begun working on my third site design/hosting case where the party with whom I am working has been literally cheated, I find that getting changes made in domain name registrations is basically too difficult."

    Protecting people's domain names is one thing, but the last three new clients who came to me were set up, robbed and then when they wanted rescue from me, my hands were tied because the information in their domain name registrations had email addresses that no longer existed and/or technical admins who had disappeared from the face of the earth.

    I spent six weeks fighting Network Solutions for one domain name - just to have the email contact changed. The original web designer/tech had closed up shop and disappeared so the email address was no longer a good one. Nonetheless NS sent an email to this bad address after I explained the situation by telephone to three separate people in the company. When it bounced they rejected the change. So my client sat, still with no web site up and running, no way to address the situation. After several faxes and more telephone calls, NS was finally persuaded to realize that the email address they were using was no good. My client tried emailing them the change, to no avail, he called them, also no good. By six weeks it was getting out of control. He had already proven he owned the name.

    I realize that anyone could contact a registrar and say I am the new web tech for whateversite.com and change things if it were too easily done, however six weeks for this one client meant a dead site and lost business.

    Case scenario number two resolved in five weeks. Also attempted through Network Solutions (now Verisign). It also took just about as much hassle as the first one.

    Currently just beginning to attempt to extract a third client from a nasty situation and this time it's with Canadian company netnation.com. Have no clue what I'll be up against, but likely the same thing. Lost time and lost business for my client who has already been cheated out of nearly $2,000 by the original web designer who simply closed up shop and disappeared.

    Is there no way to provide an authority of some type to verify members who are legitimate so that these changes can occur with better timing and people do not lose more money than they already have? I would even pay for such a membership.

    If anyone else had faced similar problems I would certainly like to hear from you. If you have found a better way to work through the difficulties and help people who have already been victimized by fraudulent web designers and can't afford more down time, I would really appreciate knowing how you managed it.

    I understand the responsibilities of registrars, but far too many people are getting a bad taste of the Internet this way. When they want to be rescued from one bad situation and have already been robbed, it seems unfair to continue to make it hard for them to obtain what actually belongs to them.

    Thank you

    Debra Dean
    Window on the World Internet Services

      ICANNWatch Login  


    [ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]

    This discussion has been archived. No new comments can be posted.
    Domain name transfer snafus | Log in/Create an Account | Top | 15 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    Re: Domain name transfer snafus
    by dtobias (dan@tobias.name) on Tuesday December 18 2001, @01:47PM (#4128)
    User #2967 Info | http://domains.dan.info/
    These stories emphasize the need for keeping the contact information for your domain name correct and complete, though this advice comes too late for your clients. When you register a domain you should always make sure you are at least one of the contacts for it, instead of letting your ISP, designer, programmer, or other person or company put everything in their own name. And if you change your postal or email address, be sure to update it in your domain record before the old address becomes invalid. Leaving incorrect info in a domain record not only makes updates more difficult, but also may be regarded as evidence of bad faith if your domain gets challenged under the UDRP.
    [ Reply to This | Parent ]
    • 1 reply beneath your current threshold.
    Re: Domain name transfer snafus
    by ldg on Wednesday December 19 2001, @02:07PM (#4150)
    User #2935 Info | http://example.com/
    Wasn't that the entire basis for the problem? Unethical practices by designers, ISPs and others should be easily eliminated by having registrants control their own domains. IMO, if you have a domain name, you should be able to understand the reponsibilities of controlling it, or have an admin you can trust - at least as much as you could trust your attorney.

    I've had some rather serious discussions with ISPs about who should control the "tech contact" information. I control my registratations and my ISP has to inform me of changes so that I can make the appropriate changes to the registration tech contact record. No one has the password to my registration accounts except one other trusted person (husband, in my case).

    One of the reasons I moved my domains from NSI (now Verisign) is that the tech contact was able to make changes to the tech and other contact records. In one or two cases, that caused me considerable problems when changing ISPs. Now I am the one who controls those changes, period. I think the scenario pointed out in the article can be avoided by registrants taking control of their own domains.

    In cases where these problems have arisen due to designers and ISPs registering domains for clients, the clients should be willing to pay the new provider for assisting in getting it all worked out. However, that resolution should include the regisration being put in the registrant's control and his or her taking responsibility for it thereafter. We're no longer in that pleasant situation where you go to your ISP for domain registration except where the ISP is a "reseller" using a connected web interface with the registrar. New interfaces are easier to use these days, so there is little need for personal intervention by a third party.
    [ Reply to This | Parent ]
    Re: Domain name transfer snafus
    by coleygross (coleygross@southbeach.homeip.net) on Friday December 21 2001, @03:20PM (#4189)
    User #3171 Info | southbeach.homeip.net

    Read the rest of this comment...

    [ Reply to This | Parent ]
    • 1 reply beneath your current threshold.
  • 3 replies beneath your current threshold.

  • Search ICANNWatch.org:

    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com