owebtw
@edu.tw
| reply to G_Poobah
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. |
|
owebtw
@edu.tw
| reply to shadow700
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. |
|
shadow700
join:2004-08-05
Collegeville, PA
| reply to raccettura
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. |
|
mikef1
Mike
join:2004-10-28
Littlestown, PA
| reply to fletchlives
Glad its not me.
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 |
|
raccettura
join:2002-09-28
USA
| reply to Briggs6
Re: Fix Yer Servers
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. |
|
G_Poobah
join:2004-01-17
Schenectady, NY
| reply to Briggs6
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) |
|
Briggs6
join:2004-10-05
Boring, OR
| reply to G_Poobah
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 | reply to DVOOR8
No, you don't understand.
There can ONLY BE ONE REGISTRAR for a domain..
Learn how the internet works before posting. |
|
DannyZ
Gentoo Fanboy
Premium
join:2003-01-29
Erie, PA | reply to DVOOR8
single point of failure? Ya, let me go get a 2nd registrar for my domains.... |
|
Necronomikro
join:2005-09-01
| reply to DVOOR8
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? |
|
DVOOR8
join:2001-12-24
USA
 ·Optimum Online
| reply to DA
said by DA  :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. |
|
DA
join:2002-04-13
Greenville, SC | reply to DVOOR8
I posted this already below, but just to repeat :
They did not host with godaddy! Godaddy was just their registrar. |
|
DA
join:2002-04-13
Greenville, SC
·Charter Pipeline
 ·ViaTalk
1 edit | reply to DA
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 | reply to fletchlives
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? |
|
DA
join:2002-04-13
Greenville, SC | reply to fletchlives
If you actually read the thread you would have seen that godaddy was only the registrar. Nectartech does host their own dns. |
|
fletchlives
@mi.charter | 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. |
|
