 | reply to James_d
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. |
|
 | 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. |
|
 | reply to Necronomikro And that's one of the things two domains with different registrars protects you from. |
|
 | 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. |
|
|
|
 | 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. |
|