61–70 of 119 posts
Earlier quoted context omitted.
Just for future reference, it's usually considered a good idea to put your status page on completely independent infrastructure so that it stays up even when the rest of your stuff goes down. A status page that doesn't work during an outage isn't particularly useful.
Like!
Earlier quoted context omitted.
I moved most of my stuff to Route53 awhile back and for the most part I don't regret it.
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.
Earlier quoted context omitted.
Was going to switch to route 53 while you guys were down and switch back, but the page says it'll take a day...Might as well just wait at that point. I know it's panic mode over there, but some kind of failover record would be awesome for when this happens in the future(or an option for one).
Everything related to DNS says it'll take a day but that's "worst case"... I've successfully transferred DNS for 5 Namecheap-registered domains to Route 53 since this all started a couple hours ago, and they're now up & running smoothly. Their "update DNS server" page was acting a bit wonky, kept saying some of my nameservers were invalid when they weren't, but I eventually got them all switched. This isn't a dig aga…
Earlier quoted context omitted.
I moved most of my stuff to Route53 awhile back and for the most part I don't regret it.
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.
We are in the process of mitigating a large scale DDoS attack against our global DNS platform. We expect service to return to normal very shortly. Stay tuned and let me know if you have any questions. ted@namecheap.com
Most DDOS attacks against a company like yours are actually attacks against a specific customer. If: a) you had a pool of DNS server names, say 20, all with unrelated hostnames b) you assigned 2 to each customer, randomly, when they configured a domain to use your servers. Then, a DDOS attack would impact 10% of your customers instead of 100%. (Assuming other practices, like null routing the target until resolved)
Earlier quoted context omitted.
Just for future reference, it's usually considered a good idea to put your status page on completely independent infrastructure so that it stays up even when the rest of your stuff goes down. A status page that doesn't work during an outage isn't particularly useful.
Good point. The status page is on another cloud but since this is a DNS issue, the subdomain is down. In the future, we'll investigate running this page on a secondary DNS.
Earlier quoted context omitted.
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 use Route 53, your zone file is still at Namecheap (registrar). Doesn't that still make Namecheap a failure point?
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".
We are in the process of mitigating a large scale DDoS attack against our global DNS platform. We expect service to return to normal very shortly. Stay tuned and let me know if you have any questions. ted@namecheap.com
We are in the process of mitigating a large scale DDoS attack against our global DNS platform. We expect service to return to normal very shortly. Stay tuned and let me know if you have any questions. ted@namecheap.com
Earlier quoted context omitted.
If the hackers really want to take you down, adding another server in isn't very hard...
If you're as big as NameCheap, you can afford to pay CloudFlare or somebody like it to protect your status page.