Hacker Newsnew | past | comments | ask | show | jobs | submit | sparagi's commentslogin

I agree. We left Network Solutions b/c they were hit 3 times in less than a year. Maybe the website targets moved to Namecheap, so they were targeted also?


We looked at Route 53, but would that make a difference today if your domain is registered at Namecheap?

If Namecheap is down, it does not get redirected.


If you don't use namecheap's dns servers, dns requests for your domain do not go to namecheap for redirection. They don't go to namecheap at all. Your specified dns servers get registered with the top level domain servers.


If you use Route 53, your zone file is still at Namecheap (registrar). Doesn't that still make Namecheap a failure point?


No. The zone file lives on the nameserver (DNS server) which Route 53 provides. Namescheap registers a list of nameservers for your domain with the TLD.

An over simplified example for looking up "news.ycombinator.com":

1. First query the TLD nameserver for all ".com" domains asking for the authoritative nameserver(s) for "ycombinator.com".

2. Next query that nameserver for "news.ycombinator.com".


But, the first entry point is namecheap. The domain is at Namecheap, so it will not find the zone file at Route 53, if Namecheap does not send it there. Right?


No, registrar's are your portal to updating data in TLDs, but those TLDs are each operated separately. .com and .net are operated by Verisign, for example.


If they messed up your cheeseburger, I could see this. How does this help this situation? It doesn't. Namecheap should take that money and invest in their infrastructure.


I'm sure they will. Just a matter of balancing stuff, of course.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: