 
fletchlives
@mi.charter | Fix Yer Servers Yeah, it's GoDaddy's fault your machines were compromised.
And what's this at nectartech.com about all the snazzy things they can do, but they can't run their own DNS? The state of the web hosting business is pathetic. | |
|
 | Sikmaz
join:2002-04-13
Greenville, SC | Re: Fix Yer Servers If you actually read the thread you would have seen that godaddy was only the registrar. Nectartech does host their own dns. | |
|
| | Sikmaz
join:2002-04-13
Greenville, SC
 ·Charter Pipeline
 ·ViaTalk
1 edit | Re: Fix Yer Servers A few other points:
1) The "abuse" issue occured two days before godaddy changed their nameserver records and was resolved as soon as the issue was reported to them.
2) Godaddy did not check with nectartech before taking action
3) Godaddy made the change late on Friday and went home without anyone available to undo the change. | |
|
| DVOOR8
join:2001-12-24
USA
·Optimum Online
1 edit | The Nectartech datacenter is completely at fault here, NOT Godaddy.com. Any company that takes money from customers for hosting and has such a huge a single point of failure that depends on a 3rd party outsourced 2nd rate hosting company isnt a very good host. GoDaddy is good for personal pages and blogs NOT serious commerce or Professional level hosting.
What the heck kind of "Data Center" relies on godaddy for the domain? | |
|
| | Sikmaz
join:2002-04-13
Greenville, SC | Re: Fix Yer Servers I posted this already below, but just to repeat  :
They did not host with godaddy! Godaddy was just their registrar. | |
|
| | | DVOOR8
join:2001-12-24
USA
·Optimum Online
| Re: Fix Yer Servers said by Sikmaz  :I posted this already below, but just to repeat : They did not host with godaddy! Godaddy was just their registrar. I understand, but a single point of failure is a single point of failure, and unacceptable for any host that takes money from people. | |
|
| | | | DannyZ
Gentoo Fanboy
Premium
join:2003-01-29
Erie, PA | Re: Fix Yer Servers single point of failure? Ya, let me go get a 2nd registrar for my domains.... | |
|
| | | | 
G_Poobah
join:2004-01-17
Schenectady, NY | No, you don't understand.
There can ONLY BE ONE REGISTRAR for a domain..
Learn how the internet works before posting. | |
|
| | | | | Briggs6
join:2004-10-05
Boring, OR
| Re: Fix Yer Servers No, you need to learn about the Internet. Especially before calling someone ignorant.
You can set more than your provider's name servers for your domain. These losers (losers being the customers and the datacentre) only had
quote:
Domain servers in listed order:
NS1.NECTARTECH.COM
NS2.NECTARTECH.COM
for a majority of their customer's domains. If they had third party name servers as slaves, the removal would have taken nothing out but the nectartech.com domain. | |
|
| | | | | |
G_Poobah
join:2004-01-17
Schenectady, NY
| Re: Fix Yer Servers Sheesh,you just prove your ignorance even more. What you are describing has NOTHING to do with what godaddy did.
The ROOT SERVER which controls the .com name was changed by godaddy ilegally. The ROOT SERVER is what tells the rest of the world where to find the DNS Server. ONLY REGISTRARS can change those records. When you pay for a registrar, they are the ones who post where your DNS Servers are located, via the ROOT SERVERS.
Get a clue..
Godaddy changed the 'whois' results, which returns the ADDRESSES of the DNS servers which service a domain. Without that information being correct (which godaddy ilegally changed), the domain DOES NOT EXIST, cause NO-ONE CAN FIND IT (except for cached copies, or local lookups) | |
|
| | | | | | |
owebtw
@edu.tw
| Re: Fix Yer Servers Sheesh, look who's ignorant...
What he is describing has NOTHING to do with what godaddy did, but it has ALL TO DO with whether or not Nectar's Data center goes offline. As most of their customers' domains use nectartech.com as nameservers, failure of the nectartech domain causes failure of all other domains. These other domains would not have had to fail if they had extra nameservers set to domains NOT controlled by GoDaddy.
In addition, it seems clear to me that phishing sites DID exist on the nectartech.com domain. It was on a customer's machine, but that machine had a NECTARTECH.COM DOMAIN!
Nectartech
1. obviously did not take the vulnerability down fast enough.
2. did not follow the directions given in GoDaddy's email AFTER they were shut down (because they kept saying it took too long that way)
3. should not have allowed the entire data center's other domains to rely on one single domain anyway
There is a second part to this phone call where you see this marc person just being an ass. The representative keeps asking him to read the email and follow the instructions and they will reinstate his domain. But he refuses to do as told, and keeps whining at them to "PUT IT BACK UP IMMEDIATELY!!" "IT'S AN EMMMMERGENCY!!" "IT'S AN EMMEEEERGENCY!!"
Why, Marc, didn't you just do as you were told?
GoDaddy had all the right to shut down the domain:
1. Phishing website is on "nectartech.com" domain name. You can see this on the page marc published the emails.
2. Godaddy says the site was not removed.
3. Godaddy shuts down website.
It does not MATTER that it was a customer's website. The offending site USED THE NECTARTECH.COM DOMAIN! If the offending website was on NectarPuke.com and they shut down nectartech.com, that would be GoDaddy's fault. From what I see, it is not. | |
|
| | | | | | raccettura
join:2002-09-28
USA
| Many large websites use multiple domains as dns servers for this case.
ns1.domain.com
ns2.altdomain.com
altdomain.com could be hosted by another registrar just for this purpose. At that point, you can then edit the domains that point to these servers to remove ns1.domain.com and your back in business.
This isn't uncommon. | |
|
| | | | | | | shadow700
join:2004-08-05
Collegeville, PA
| Re: Fix Yer Servers Oh. My. God.
How many rows are on the bus that picks you up each morning? 3, maybe 4?
I don't know how it can be explained any simpler than it already has.
The list you gave contains AUTHORITATIVE NAME SERVERS for the DOMAIN. Yes, you can have names servers at different providers.
However, the list itself is provided by a single REGISTRAR. You can have only one REGISTRAR per domain.
In this case, GoDaddy, the REGISTRAR, changed the AUTHORITATIVE NAME SERVER list so that the DOMAIN was effectively shut down. For example, instead of listing:
ns1.domain.com
ns2.altdomain.com
It listed:
ns1.otherdomain.com
ns2.otherdomain.com
which were two NAME SERVERS which were NOT AUTHORITATIVE and did not have configurations for the DOMAIN in question, therefore all DNS lookup requests FAILED. | |
|
| | | | | | | |
owebtw
@edu.tw
| Re: Fix Yer Servers No, you are the ignorant one.
The entire data center went down because all the customers' domains had the nameservers set to ns1.nectartech.com and ns2.nectartech.com. The loss of the nectartech domain resulted in the failure of hundreds of other domains, because all these domains had NECTARTECH as their nameservers. If nectartech had added a second domain from a different registrar, all these other domains would not have been affected. Only nectartech.com would have been affected. | |
|
| | Necronomikro
join:2005-09-01
| So, how does the fact that they don't have a redundant DNS server make them liable? It was still godaddy that took them down. And, even if they had a secondary DNS entry, that was valid and hosted from a different DNS company, godaddy CHANGED THE DNS RECORDS. They changed them to 'NS1.SUSPENDED-FOR.SPAM-AND-ABUSE.COM'. Your arguments about redundancy aren't very valid. They also didn't take down the domain at fault - instead, they took down the NS domain.
So, if I am at a shooting range and miss the target and hit a window, the person with the window is responsible, since they should have had a guard over it, or a redundant window that could be immediately pulled down? | |
|
| 
mikef1
Mike
join:2004-10-28
Littlestown, PA
| My web host and registrar is more expensive than most of your typical hosting/dns providers. Every once in awhile I think about switching to save some cash, but then I hear stories like this and happily pay the extra for top notch.
--
mike
HouseOfMike | |
|
|
| DVOOR8
join:2001-12-24
USA
·Optimum Online
| Re: This guy is a serious whiner! You are 110% correct.
The Nectartech datacenter is completely at fault here, NOT Godaddy.com. Any company that takes money from customers for hosting and has such a huge a single point of failure that depends on a 3rd party outsourced 2nd rate hosting company isnt a very good host. GoDaddy is good for personal pages and blogs NOT serious commerce or Professional level hosting.
What the heck kind of "Data Center" relies on godaddy for the domain? | |
|
| | Sikmaz
join:2002-04-13
Greenville, SC
·Charter Pipeline
·ViaTalk
1 edit | Re: This guy is a serious whiner! said by DVOOR8 :You are 110% correct. The Nectartech datacenter is completely at fault here, NOT Godaddy.com. Any company that takes money from customers for hosting and has such a huge a single point of failure that depends on a 3rd party outsourced 2nd rate hosting company isnt a very good host. GoDaddy is good for personal pages and blogs NOT serious commerce or Professional level hosting. What the heck kind of "Data Center" relies on godaddy for the domain? Read the thread, they did not host with godaddy! Godaddy was just their registrar who changed their nameservers on them to take them offline because of a abuse report but never verified the report.
From what I understand they host with multiple datacenters for redundancy.
To use an analogy, you bought your domain from godaddy but host your nameservers and web servers with rackspace. Your server gets compromised, you catch it after a few hours and fix it.
Two days later godaddy gets an abuse report and goes in and changes your nameserver records to point to something else to take you offline without checking to see if the issue was resolved. They do this on a friday without telling you and go home without any recourse for you to get it fixed until monday.
Is that clearer? | |
|
| | | 
LiamJunket
Premium
join:2002-03-03
Ocean City, NJ
·Comcast
| Re: This guy is a serious whiner! said by Sikmaz :Read the thread, they did not host with godaddy! Godaddy was just their registrar who changed their nameservers on them to take them offline because of a abuse report but never verified the report. From what I understand they host with multiple datacenters for redundancy. To use an analogy, you bought your domain from godaddy but host your nameservers and web servers with rackspace. Your server gets compromised, you catch it after a few hours and fix it. Two days later godaddy gets an abuse report and goes in and changes your nameserver records to point to something else to take you offline without checking to see if the issue was resolved. They do this on a friday without telling you and go home without any recourse for you to get it fixed until monday. Yes, godaddy was clearly at fault here. And the mgt at godaddy should have made their abuse dept head available to resolve the issue, weekend or not. As head of the network engineers at my company, I was available 7/24 to data center mgt when problems occurred.
--
--
Join Red Room Forum
My Web Page | |
|
| | | | DVOOR8
join:2001-12-24
USA
·Optimum Online
| Re: This guy is a serious whiner! said by LiamJunket :said by Sikmaz :Read the thread, they did not host with godaddy! Godaddy was just their registrar who changed their nameservers on them to take them offline because of a abuse report but never verified the report. From what I understand they host with multiple datacenters for redundancy. To use an analogy, you bought your domain from godaddy but host your nameservers and web servers with rackspace. Your server gets compromised, you catch it after a few hours and fix it. Two days later godaddy gets an abuse report and goes in and changes your nameserver records to point to something else to take you offline without checking to see if the issue was resolved. They do this on a friday without telling you and go home without any recourse for you to get it fixed until monday. Yes, godaddy was clearly at fault here. And the mgt at godaddy should have made their abuse dept head available to resolve the issue, weekend or not. As head of the network engineers at my company, I was available 7/24 to data center mgt when problems occurred. What the issue is here is that the NectarTech datacenter has determined a sinle point of failure that relies on a 2nd rate hosting company is acceptable. | |
|
| | | | |
LiamJunket
Premium
join:2002-03-03
Ocean City, NJ
·Comcast
| Re: This guy is a serious whiner! said by DVOOR8 : What the issue is here is that the NectarTech datacenter has determined a sinle point of failure that relies on a 2nd rate hosting company is acceptable. And you keep ignoring the fact that godaddy was NOT the hosting company but the registrar and that the actions they took as registrar were completly outside normal business practices. And your logic was refuted multiple times in the webhosting thread as well. »webhostingtalk.com/showthread.ph···2&page=5
--
--
Join Red Room Forum
My Web Page | |
|
| | | | | | jeffyjeff777
join:2002-06-01
Collegedale, TN | Re: This guy is a serious whiner! From my experience with them, godaddy sucks in every aspect  | |
|
| | | datanetdude
join:2005-08-13
San Antonio, TX
| Hello!!! Hosting!!! Hosting is just that...Hosting... Godaddy was hosting all their domain records! That is why I said I would never host with GoDaddy. You just assumed since I mentioned family photos, hobby pages, etc. that I was referring to them hosting their site. If I did not listen to the .mp3 I would not have been able to make my previous post. You are forgiven though! Just don't let it happen again
P.S. I have had parked domains at GoDaddy and their uptime seriously sucks  Only a (edited) would host with Godaddy! | |
|
| | | | 
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC | Re: This guy is a serious whiner! Sigh. GoDaddy was NOT hosting ANY of their domain records. They were hosting their own DNS, running their own DNS servers. GoDaddy hijacked the domain by changing the nameservers to point to GoDaddy. | |
|
| robct
rob
join:2004-04-09
Waterbury, CT | You obviously have NO clue what a datacenter is. They aren't "hosted" with GoDaddy. | |
|
IronChefMoto
Premium
join:2001-02-08
Alpharetta, GA
2 edits | Ya know... It's OK with me that they did this. If it's something that can be resolved Monday morning with GoDaddy, so be it. In this day and age of ridiculous scams and spyware and shit, it only takes one script-churning machine to start a whole helluva lot of shit.
If GoDaddy acted in NOT so timely a fashion, so be it. They may have processes that outsiders aren't aware of. What they did, though, is respond with those processes (regardless of timeliness) and shutdown the domain from where the phishing abuse notice came from.
If Nectartech.com doesn't like it -- they can friggin' get another registrar. Sounds to me like they need to screen their customers and/or improve their internal security to prevent phishing scripts from running in the first place. I don't give a crap that they found the machine, fixed the problem and THEN, 1-2 days later, were hit with a change from GoDaddy.
GoDaddy had a process, Nectartech had a process. Seeing as GoDaddy is just a registrar in this case, there's no expectation that "synchronization" of abuse tickets should've happened here. It just happened. For all GoDaddy knows, Nectartech could be a third rate shopping mall computer repair shop -- IF the only relationship involved here is as a registrar.
Maybe some extra fees should be added to a registration for ALL registrars that flags a domain registration as tied to a major data center. Make Nectartech and 1000s of other data centers pay an extra $20/year or more to flag their operations as UNIQUE in the realm of porn domain names and cybersquatters. When something DOES go wrong and a ticket comes in to a registrar complaining of abuse or whatever, they'll see the flag and know that, "Hey, this domain customer needs to be contacted before I do anything to their domain."
NO -- I don't do business with GoDaddy, but I've read up on the company, and I appreciate that they try and bring lower prices to domain registration. That, and their spokesmodel has nice tits. Sue me.
IronChefMorimoto
--
Shuttle SN85G4V3 (Gaming/Development): AMD Athlon64 3400+ | ATI 9800 Pro 256MB
Dell Latitude C810 (Work/E-Mail): Intel PIII-M | Onboard Video
Shuttle SK41G (Wife): Athlon XP 1800+ | Onboard Video | |
|
James_d
join:2005-08-27
uk
| Whee, screwups all around. Well, if anyone is a hosting provider and is using godaddy as their sole nameserver domain registrar, the message is clear: fix that ASAP. If you're a customer of a hosting provider, time to check that you have nameserver addresses from two different providers and tell your provider their business if they aren't providing you with them. And remember that you are supposed to make sure you have two nameservice providers as well - losing your provider's nameserver(s) shouldn't take you out.
Nectartech seems to have been poorly configured, not an encouraging sign. Their customers should probably reconsider their positions, since this was an avoidable outage apparently caused by a design flaw in the Nectartech system (dependence on a single name service provider, a known bad practice).
Also time to rethink use of godaddy for name service, since it seems to have abused its position. Rationale:
1. Abuse emails which must be responded to apparently sent to the domain which was shut down, making it unlikely that they would be received.
2. A godaddy rep asserted that they were aware that they had shut down a hosting data center because of the actions of a customer of the hosting center after the hosting location had dealt with their own customer.
3. Godaddy acted against the host rather than the compromised domain. Godaddy doesn't seem to have much reason to be involved in this.
4. In a subsequent call a godaddy rep stated that there was nobody from abuse around and that without someone in abuse the problem couldn't be fixed. 24/7 turn off without 24/7 turn on isn't adequate.
5. Hacked boxes in hosting locations are inevitable and it seems that godaddy is willing to kill the hosting business when that happens.
6. Godaddy apparently sent customer-specific email to an address given by someone who had previously claimed not to be its customer. That appears to be a potential vulnerability to social engineering attacks. But I don't know if this opening could have been extended beyond this particular abuse incident or not.
7. A complete failure of proportionality. A single phishing or spamming box, even if still active, is not sufficient reason to take down a hosting provider and refuse temporary service restoration.
8. Godaddy not accepting temporary verbal contract term agreements in an emergency after claiming that the calls would be recorded. Not that it mattered in this case, because the person calling wasn't able to enter into agreements with them because it wasn't their customer.
The customer screwed up pretty majorly in several ways but this is just based on the godaddy rep claims and actions. Two of the customer screwups:
A. All nameservers depending on a single provider, godadday. Godaddy shouldn't have been given the power to take both nameservers out. The data center customers should have been supplied with at least two nameservers in different domains so godaddy couldn't compromise them all.
B. Godaddy's customer wasn't the one calling godaddy. The wrong person was calling them.
Observations:
i. Godaddy had locked the domain so it wasn't possible to transfer it to get out of the mess, as some suggested. | |
|
| Necronomikro
join:2005-09-01
| Re: Whee, screwups all around. said by James_d :Well, if anyone is a hosting provider and is using godaddy as their sole nameserver domain registrar, the message is clear: fix that ASAP. If you're a customer of a hosting provider, time to check that you have nameserver addresses from two different providers and tell your provider their business if they aren't providing you with them. And remember that you are supposed to make sure you have two nameservice providers as well - losing your provider's nameserver(s) shouldn't take you out. ... That's nice and all, but, godaddy, the registrar, changed their NS entries to 'NS1.SUSPENDED-FOR.SPAM-AND-ABUSE.COM or something like that. | |
|
| |
Die Daddy Die
@sonnet.com
| Re: Whee, screwups all around. Yep, Go Daddy needs to die NOW. What they did should sign their death warrant. Even if they don't die, it is going to cost them a LOT of business, because all other hosting companies out there are going to take stuff to a registrar who knows how to operate in their customers' interests.
To any one who is clueless out there, this is NOT Nectartech's fault AT ALL.
HOWEVER, it might be good practice from now on to have your secondary DNS be a domain that is hosted at a different registrar. It MIGHT prevent things like this from having the serious effect they did:
NS1.NECTARTECH.COM (registrared at Die Crappy)
NS2.NECTARTECH.NET (registrared at Network Solutions)
Die Crappy might not have been able to take out the NS2 under that scenario. | |
|
| | James_d
join:2005-08-27
uk | And that's one of the things two domains with different registrars protects you from. | |
|
| | |
Die Daddy Die
@sonnet.com
| Re: Whee, screwups all around. And that's one of the things two domains with different registrars protects you from.
There are almost zero protections from registrars; You may remember when panic.com had their domain stolen from them from a registrar that wasn't even theirs. You can't have a single domain with more than one registrar, so there is no way to protect from it.
Likewise, it is not clear whether having each of your nameservers be on a separate domain at separate registrars would protect you from Die Daddy. If they modify the ROOT server records for both/all of your nameservers regardless of where their domain is registered, you're still dead. Which is what Die Daddy should be as well. | |
|
| | | | James_d
join:2005-08-27
uk
| Re: Whee, screwups all around. Yes, I remember the Panix mess. If godaddy went in and modified the root record for a customer not its own the inappropriateness should be completely obvious, as would be the corrective action and appropriateness of great urgency on godaddy's part in taking that action.
In that case, it might be a crime, since I assume it does not have authorised access to the records of those not its customers, who have no agreement with it. | |
|
|
owebtw
@edu.tw
| 3. Godaddy acted against the host rather than the compromised domain. Godaddy doesn't seem to have much reason to be involved in this.
The host WAS the compromised domain. The URL was:
»69.50.229.44.ip.nectartech.com/f···ndex.php
The phising website WAS on the domain "nectartech.com"
GoDaddy maintains that the phishing site was NOT removed.
The reason all the other domains in the data center went offline was due to the fact that nectartech set the nameservers of all their customers' domains to ns1.nectartech.com and ns2.nectartech.com. The entire datacenter is relying on the single domain "nectartech.com". Any failure of that SINGLE domain would render the ENTIRE datacenter and ALL other domains in the datacenter USELESS.
That's pretty stupid of them, IMHO. | |
|
| | James_d
join:2005-08-27
uk
| Re: Whee, screwups all around. I _hope_ godaddy abuse knows the difference between the generic names assigned to servers at a hosting company and the real domain at the site, which today is reported as www.Climaxmanila.com by www.whois.sc:
1 domains found on 69.50.229.44
Showing all 1.
Website
www.Climaxmanila.com
I also hope that abuse standards at godaddy do require acting against the offending domain, not its hosting company just because the address happens to be within the range the hosting company has and assigns to its hosted customers.
If this was the case at the time of the problem, godaddy could instead have chosen to act against the customer of its which controlled the box, because Climaxmanilla.com uses godaddy for its own domain name registration and godaddy could have shut that down instead. Interestingly:
Registrant:
The Plan C Group
Registered through: GoDaddy.com
Domain Name: CLIMAXMANILA.COM
Domain servers in listed order:
NS1.CLIMAXGLOBAL.COM
NS2.CLIMAXGLOBAL.COM
For complete domain details go to:
»who.godaddy.com/whoischeck.aspx
Climaxglobal.com is also registered with godaddy, so if godaddy wanted to shut down a nameserver, it also had an option there.
So, if these were the facts at the time, a little basic research would have told godaddy abuse who it should have been shutting down, if anyone. And that someone is not nectartech.
My apologies to climaxmanilla, climaxglobal and godaddy if these were not the facts at the time of the incident. | |
|
kapil
The Kapil
join:2000-04-26
Chicago, IL
|  Oh Dear God!
GoDaddy wasn't "hosting" anything...they were just the registrar for the domain....and all they did was change the NS records associated with the domain in question. ...and since that domain was used to host DNS servers, when that domain fell off the internet, so did the domains that were using it for their own DNS.
All I have to say is that anyone who uses GoDaddy for their domain registrations, especially for business, deserves what they get.
You get what you pay for.
The ONLY thing GoDaddy can possibly be useful for is for bulk purchases of domains that are not active and purchased for speculation etc. Even then, the wholesale rate I get from my registrar is LOWER than GoDaddy's pricing. | |
|
coppertrail
join:2006-01-10
Cleveland, OH
| Lessons to be learned 1. Register the domain with a more business oriented company. I agree that Godaddy is more geared towards personal web sites. Check their abuse and domain suspension policy before registering with them.
2. Don't be accusatory with CS/TC. I've learned this in the past. I've gotten much better results with the "there is a problem, can we resolve this?" approach. I'm not saying one was right or the other was wrong. Just that being accusatory generally puts folks on the defensive.
Did GD do anything wrong? We need more information as to exactly what happened, what the results of the breach were, their reasons for suspending the domain. If Godaddy was following their documented domain suspension policy, they were in the right.
Also, when the breached machine was corrected, was this information immediately communicated to GD? There are lots of other factors that we simply don't know. | |
|
Packetloss
Premium
join:2002-07-01
Harrisonburg, VA
| Get away from GoDaddy.com I do not care what happened, Godaddy knew it was a hacked server that someone else used to commit the spam not the paying customer, instead even though the problem was fixed they still took him offline, that is not providing any level of service when you take down an entire data center. I would think he will move after all these, but I would hope GoDaddy would have some liability due to the fact they refused to assist him for 24 hours, advertising 24 hour support on their site, but not defining "limited" support.
When I started out in the business Godaddy was decent, they have turned into a nag company, every time you purchase anything form then you have to do thur numerous loops of them trying to sell you add ons.
I heard at other places they love to turn off domains to have the owners pay a fee to turn them back on, from what I understand this has happened many times before with other people.
I had over 70 domains at once with these guys, I have been slowly moving them off their servers. Their are other good providers like namecheap.com that offers a lot more for less without the hassle.. Again get away from GD! | |
|
tidal
Tidal
Premium
join:2001-01-18
Madison, AL | So it begins... having ISPs police the internet *sigh*
the beginning of the end
godaddy is also shutting torrent sites. | |
|
| 
techjoe
Premium
join:2004-02-20
Schererville, IN
 ·Sprint Mobile Broa..
| Re: So it begins... All within their TOS and AUP I'm sure, as I see nobody waving them around yet.
"You get what you pay for." In this case, Godaddy obviously doesn't want to be assosiated with a high-risk client, or something along those lines. They never really claim to be that sort of host either, as many others have said..
--
www.clanc.cc | |
|
insomniac84
join:2002-01-03
Schererville, IN | I don't understand... Why would the domain company be responsible for spam coming out of someone else's server? It seems messed up when your domain host is going to try to control what's running on your servers. | |
|
bmn
? ? ?
Premium,ExMod 2003-06
join:2001-03-15
hiatus
·Packet8
| I've been looking for an excuse... To get away from GoDaddy for awhile now and this seems to be a good one... For a registrar to suspend a domain, unilaterally, because it is hosting a compromised service is plain wrong because that is NOT the role of a registrar. Registrars are only the domain ownership record keepers, nothing more. If there is a problem, complaints are supposed to be forwarded to a domain's technical or administrative contact and then the domain owner becomes responsible for the problem. What GoDaddy has done here is equivalent to taking the law into its own hands in spite of there being a well established practice of contacting people in a certain order. | |
|
quetwo
That VoIP Guy
Premium
join:2004-09-04
East Lansing, MI
| Just from experience... I owned a hosting company in the late nineties through 2005. One of the biggest thing with owning a services company is knowing who you are dealing with, and making sure those business relationships are solid. Having the servers in your air-controlled, power-redundant location is only half the battle. You also have to be worried about your ISP, ARIN, DNS, the Phone Company, etc.
When I deal with a company, I make sure that the company has my interests in mind -- to that effect, I don't deal with companies that, for example, don't offer to have an account rep assigned to my account. I will PAY to make sure that somebody is looking out for me, because god knows I have too much stuff to look out for.
GoDaddy has never offered such a thing. They are for people looking for a cheap domain that they don't get full access to. Register.COM, NetSol, etc. all give you FULL access to the SOA record of your domain. Registrars that don't should NOT be an option for your company, let alone a hosting company.
Just another thing you need to check when looking for a shared-host. Who do they register through? Two clicks will tell you loads about how the company is setup. | |
|
packetscan
Premium
join:2004-10-19
Bridgeport, CT
clubs:
·Optimum Online
| redundant This is redundant however it's always a good idea to have more that two domain names and dns servers in multiple locations(data centers).
{Feature-Request} Special Consideration for people that are using the name for hosting purposes like in this case an ISP. Go daddy or any registrar for that matter could have known the potential impact it would have caused.
--
Who do you want to pay off today? | |
|
mperkel
join:2000-12-18
Gilroy, CA
| I'm the guy who made the recordings Several of you don't have any idea what a data center is. Nectartech is a hosting company that does web hosting, dedicated servers, and coo customers. I'm one of thise customers.
First - the recordings:
»marc.perkel.com
You'll find the links there.
Now - as to the single point of failure stuff. Generally people assume that the registrar will not just turn your domain off. An assumption that I'm rethinging after this event. For those who are critical of not thinking of this earlier I would point out that the same thing can happen to 99.9% of all domains, including the big ones. Example include:
broadbandreports.com
yahoo.com
microsoft.com
ebay.com
ibm.com
paypal.com
aol.com
So - if the registrar of the above domains nuked the DNS for the domain of the name server then they would be off the internel. Not only that but in the case of yahoo and aol, all their customer's domains would go down as well. | |
|
|
See 7 replies to this post |
|
Icspots
@advances.net
| Godaddy has there rights too I think hearing your conversations record that you didn't want to follow a companys procedures and didn't want to to take the time to read the email they had send you. Then you bash Bush in your site of doing illegal stuff but then again you go record conversations illegally without letting the person know (2nd conversation) | |
|
|
Die Daddy Die
@sonnet.com | Re: Godaddy has there rights too If I were mperkel and Nectartech, I'd be calling the FBI.
Go Daddy has the following rights:
The right to remain silent.
The right to an attorney; if you can not afford one, one will be appointed to defend you. | |
|
|
Mtav80
Premium
join:2002-12-28
Loveland, CO
·Comcast
| Moving from go daddy now If it was hosted on go daddy servers it would make a little more sense. But since it was just go daddy the registrar it looks like a abuse of power.
I will be moving my domain off go daddy after reading about this and listening to the recorded call. Can anyone give me feedback on namecheap.com. From what little I have gathered they looked to be a reseller of enom.com I think. | |
|
JoeSchmoe007
join:2003-01-19
New York, NY
| But where do you move? I don't care to discuss who is right or wrong here. But I think that company like GoDaddy should have someone in the office who can resolve that kind of problems 24x7. So all of you screaming "OMG GD SUCKS! I AM MOVING ALL MY DOMAINS!" - where do you move? Do you know for a fact that company you move to has mechanisms in place to avoid such situations? | |
|
sweintz
Premium
join:2002-03-01
Hamden, CT
| GO Daddy did exactly as they should have done Here's what happened:
The phishing script complaints to netarch.com go all the way back to at least November. Nectartech.com had been notified, yet chose not to address the issue apparently.
The only way at that point to get the phishing site offline was to pull the registration. Something that godaddy's TOS/AUP allows for in cases such as this.
Put the blame where it belongs - with Nectartech.com | |
|
| scurby2
join:2003-11-16
Long Beach, CA | Re: GO Daddy did exactly as they should have done I hope they have another Big Jugs girl commercial during the super bowl | |
|
| |
CSITECH1
| Re: GO Daddy did exactly as they should have done Damn A Bunch Of Porn Sites Got Knocked Off The Net....
Yeah I Think They Better Call The FBI.....:D | |
|
manfmmd
Premium
join:2003-01-14
Earth
clubs: | Marc....... Hang up the phone and follow the directions in the email... | |
|
| ericdaboy
join:2005-09-21
West Palm Beach, FL
| Re: Marc....... That is what I couldn't understand about the call.
First he was a "friend" of the person this happened to.
He got the job of calling GoDaddy instead of the person that this happened to. First thing that made me cringe is that he was upset "for this friend." Why? Why make your bloodpressure go up for something that is not your problem?
Second, I absolutely hate when a person/customer uses the "YOU" or "YOU PEOPLE." No WE didn't do anything. You get more with honey than you do with vinegar. He should've calmly stated, "We have a problem and I'm hoping you can solve this immediately."
Third, WHY didn't he read the email and follow basic instructions? He kept freaking stating THIS IS AN EMERGENCY! Why is it? Is national security at risk? Is this terrorist related? Is this your company? No. None of the above. Read and follow the instructions. He couldn't read the email or find the email because he did not have the email.
Both sides are at fault - but the customer shouldn't be calling up, freaking and pushing the buttons of everyone who answers the phone. In tech support, you do that, NO ONE will help you. | |
|
SilenceGold
Premium
join:2003-07-31
Benton, AR | Illegal? I wonder if a law was broken with GoDaddy's action? or is it listed in their AUP/TOS that they are able to do the domain server changes? | |
|
|
|
|
GoDaddy.com Takes Down Data Center
This guy is a serious whiner!
