The consequences can be embarrassing, costly, and time consuming. When you lose your domain to someone else, you must reprint your stationery with new Web addresses, send out releases to your customers confessing your mistake, and lose untold email messages when your email vanishes into the ether (or worse, goes to the domain's new owner).
But in most cases, it's easy to avoid problems like these. So learn a few lessons from four organizations that recently lost their domains. Take heart that two of them have got their domains back again-but don't assume that you will have the same good fortune as they did. Prepare for the worst-and be happy when it doesn't happen to you.
The domain had expired, "dropped" back into the public domain, and been snapped up by a speculator. The previous owners of the domain "fixed" the problem by registering the .net version of the domain and hosting their site there. The MacSlash community rallied round the cause and registered the .org and .info versions of the domain too. And word spread quickly about the new location of the site.
The MacSlash story has happy ending: The issue became a cause celebre in the Mac community and pretty soon, things got too hot for the new registrant, who returned macslash.com to its original owner.
But not everyone is so lucky.
But in May of 2002, the domain expired without notice from the registrar, and was subsequently re-registered by a portal company based in Hong Kong. Ultimate Search redirected the user group's former domain to a generic portal with links flashing online casino ads and links that generate revenues for the company on a pay-per-click basis. As of this writing, the user group has not regained control of its domain. However, it continues to operate its site at pibmug.com.
Naturally, domain registrars are all too keen to keep their customers-the competition among domain registrars is fierce. The governing body of the .com domain system, ICANN, has accredited more than 50 registrars, and hundreds more companies resell domain services. So most registrars send out not one but several reminders to their customers to re-register their domains early and often.
Both MacSlash and PIBMUG used the registrar Dotster, which sends out automatic reminders at T-minus 45 days, 30 days, and 15 days before the domain expires. In fact, Dotster is so vigilant, the company even sends out reminders to former clients who have transferred their domains to other registrars.
But MacSlash and PIBMUG did not get their reminders. The jury is still out as to what happened with PIBMUG, but MacSlash traced the problem to over-vigilant spam filtering. When the group registered macslash.com, they used Apple's iTools email service, which provides free email at the mac.com domain. Unfortunately, the service's spam filtering treated repeated requests to renew domains as unsolicited commercial messages, and threw them into the bit bucket.
The .com registry, run by Verisign's Network Solutions division, holds on to all the expired domains until it's ready to "drop" them en masse back onto the market.
And once an expired domain drops, it's up for grabs by anyone with $10 to $35 to spare. And an entire aftermarket has sprung up around expired domains. Companies like DomainsBot, The Unclaimed, and Daily Expired Domains compile lists of on-hold domains for subscribers, and domain registrars including Network Solutions and Dotster maintain services for their subscribers to snap up domains as soon as they drop.
The aftermarket for expired domains creates a feeding frenzy among speculators, which is bad news for domain holders who let their domains expire. Once a domain is reregistered, the only recourse the original domain owner has is to go through ICANN's dispute resolution process (which is outlined at www.icann.org/udrp). During disputes, ICANN tends to favor copyright holders and people with legitimate claims on a domain-which would act in favor of PIBMUG's claim against Ultimate Search. But the process is a time consuming hassle, and ICANN doesn't give preferential treatment to previous owners of domains who let them expire.
The theater found free hosting for its Web site at GeoCities, and rigged up an ad-laden version of their site there. But nobody involved know how to handle the domain issue, so they had to change their Web address at the various arts and theater portals, search engines, and periodicals that listed them.
When the domain finally expired, a fan of the group snapped it up and arranged for new hosting for barnstormerstheater.com at a local community site.
But unlike Barnstorm's good fortune, there are disasters.
At the time, there were no plans for a public Web site, but last year, an office manager submitted plans and a project management timeline for a public site that she could develop and manage herself. When she came to register the Authority's domain name, she found that the .com, .net, and .org versions had all been registered years earlier. The registrant was their IT company, which used the names as a bargaining chip for taking control of the Web development project-a potentially lucrative contract.
Record last updated on 1-May-2002.
Record expires on 12-Oct-2004.
Record created on 12-Oct-1999.
Plug that "record expires" date in big bold letters into your PIM, your diary, and your wall calendar. Tattoo it on your wrist if you need to, but make sure that a month before that date, you pay the registrar for another year or two of registration.
Of course, it also prevents "slamming" by unscrupulous registrars who send bogus domain renewal notices that actually transfer your domain to a new registrar. You don't lose control of your domain this way, but you often end up paying more or losing services like free hosting or e-mail forwarding. And even high-profile companies like Network Solutions seem to regard this as a legitimate marketing tool.
Anticipate this behavior, just in case someone manages to get control of your main Web domain. If you have the .com, .net, and .org versions of your domain name in reserve, all redirected to your main site, you'll have an instant quick fix for any domain napping problems. Sure, this will set you back a few bucks-but it gives you more flexibility in the long run.
And it's pretty good for bragging rights too.
Copyright (c) 2002 by Matt Lake. Reproduced with permission. Article reproduction coordinated by Steve Bass, Pasadena IBM Users Group.Matt manages two dozen domains, and maintains a domain buyer's guide called RegSelect. Matt Lake manages two dozen domains, and maintains a domain buyer's guide called RegSelect. Matt has written for many publications, including PC World, CNET, Computer Currents, and ZDNet. You can reach him at webmaster@regselect.com, because his spam filter's is never set beyond "Stun."There is no restriction against any non_profit group using the article as long as it is kept in context, with proper credit given to the author. This article is brought to you by the Editorial Committee of the Association of Personal Computer User Groups (APCUG), an International organization to which this user group belongs.
For more information on the Tulsa Computer Society click here