Go Daddy Reports More Than 20,000 Registered .me Domains
Domain registrar Go Daddy said it has seen a "Super Bowl-like spike in traffic and domain registrations" when .me domains became available. The company said that it registered more than 20,000 .me names within the first 24 hours of availability.
Due to server overload, "some" customers apparently registered domain names that were already taken or reserved by the .me registry before launch, which included domains for government use as as well as domain names "scheduled for a later release". The company said that it has begun processing refunds to customers of the invalid registrations.
13
Comments
Apple Says Sorry Again and Gives Away Another Free Month of MobileMe
- Locations of UK's First Best Buy Stores Revealed
- Motorola Sues Former Employee
- Facebook Sues German Social Networking Website
- The IPhone Finally Pwned, But Still Locked
- Icahn Takes A Seat In Yahoo's Board Room
- LCD Panel Pricing Trending Toward Production Costs In Some Segments
- U-Tech Hopes To Benefit From Wal-Mart Sales Promotion Of BD Movies
- Internet Math: Google Gets $1.10 Of Every New Ad Dollar
- Airline Internet Will Rely on 4G, Snubs WiMAX and CDMA
Apple Battling Acer For Third Spot in US Computer Shipments
- Apple Battling Acer For Third Spot in US Computer Shipments
- EA Extends Tender Offer For Take Two For Fifth Time
- Dear Apple, Jesus Would Be Mortified!
- iPhone 3G Fetching Outrageous Prices on Craigslist And eBay
- Apple FY 08 Third Quarter Earnings Preview
- Would You Like Lime With That
- Apple Sells 2.5 Million Macs In Q2
- Smartmirror To Tantalize US Drivers
- Craigslist Scammer Pretends To Be Father Of Fallen Soldier
- Rumors Surface of a MacBook Touch
whats a .me domain?
.me domain:
.me is an Internet country code top-level domain (ccTLD) that has been assigned to Montenegro.
http://en.wikipedia.org/wiki/.me
Normally, this is called lame programming, not server overload.
I second that. If there would be any problem, it would be that their database servers would temporarily fail. But just 20,000 transactions in the first 24hrs? With the resources they can muster (w/o breaking a sweat and their bank account), no doubt they handle 10x that load. Can anyone w/ half-a-brain justify going against basic database design/programming to allow duplicate entries? Upper management screw-up? Or there is money to be made during the refund process?
Normally, this is called lame programming, not server overload.
I second that. If there would be any problem, it would be that their database servers would temporarily fail. But just 20,000 transactions in the first 24hrs? With the resources they can muster (w/o breaking a sweat and their bank account), no doubt they handle 10x that load. Can anyone w/ half-a-brain justify going against basic database design/programming to allow duplicate entries? Upper management screw-up? Or there is money to be made during the refund process?
Normally, this is called lame programming, not server overload.
I second that. If there would be any problem, it would be that their database servers would temporarily fail. But just 20,000 transactions in the first 24hrs? With the resources they can muster (w/o breaking a sweat and their bank account), no doubt they handle 10x that load. Can anyone w/ half-a-brain justify going against basic database design/programming to allow duplicate entries? Upper management screw-up? Or there is money to be made during the refund process?
Normally, this is called lame programming, not server overload.
I second that. If there would be any problem, it would be that their database servers would temporarily fail. But just 20,000 transactions in the first 24hrs? With the resources they can muster (w/o breaking a sweat and their bank account), no doubt they handle 10x that load. Can anyone w/ half-a-brain justify going against basic database design/programming to allow duplicate entries? Upper management screw-up? Or there is money to be made during the refund process?
Normally, this is called lame programming, not server overload.
I second that. If there would be any problem, it would be that their database servers would temporarily fail. But just 20,000 transactions in the first 24hrs? With the resources they can muster (w/o breaking a sweat and their bank account), no doubt they handle 10x that load. Can anyone w/ half-a-brain justify going against basic database design/programming to allow duplicate entries? Upper management screw-up? Or there is money to be made during the refund process?
Normally, this is called lame programming, not server overload.
I second that. If there would be any problem, it would be that their database servers would temporarily fail. But just 20,000 transactions in the first 24hrs? With the resources they can muster (w/o breaking a sweat and their bank account), no doubt they handle 10x that load. Can anyone w/ half-a-brain justify going against basic database design/programming to allow duplicate entries? Upper management screw-up? Or there is money to be made during the refund process?
Wow, sextuple post, that takes talent.
What the!?!
). When I submitted my reply, I kept being redirected to a page w/ hardly any content (forgot the link). Ofcourse I checked back and when my post wasn't there, I tried again (after a minute or two). And again, I'm redirected to an empty page.
Sorry for that (though thanks gm0n3y
Oh boy, Tom's got a real problem w/ their comments script X(
Darn it, Tom!
Here's the link, http://www.tomsguide.com/us/comments/
Still a blank page. No further redirection.
I'm using Opera 9.51. Anyone else w/ the same browser/version having the same problem?
Should I try for the record number of post?
I find that about 75% of the time when I make posts, I get redirected to an error page. I guess I've just gotten used to it.