9 ms·
DDOS on Namecheap Free DNS and Default DNS V2
- micah63 13y agoyup, our app is down : (
- avb 13y agoAny good suggestions for alternative DNS providers?
- zrail 13y agoI moved most of my stuff to Route53 awhile back and for the most part I don't regret it.
- jschuur 13y agoPricing doesn't seem too bad. $0.50 for a zone (domain) and $0.50 for a billion queries: http://aws.amazon.com/route53/pricing/ http://aws.amazon.com/route53/pricing/
- jyap 13y agoCorrection on the queries pricing: $0.500 per million queries – first 1 Billion queries / month $0.250 per million queries – over 1 Billion queries / month
- zrail 13y agoYep. I had been hesitating on moving more domains over to Route53 because I thought the per-zone pricing was fixed at $0.50 per domain, but it actually scales really well. I'm going to move the rest over to Route53 as soon as I have a chance.
- toomuchtodo 13y agoWe're using Route 53 in production to handle hundreds of millions of queries per month. We're happy with it, and the price is reasonable. Also, service checks with failover is heavenly.
- benmorris 13y agoI've considered doing this also!
- jmreid 13y agoYes, Route 53 has been great for me as well. I have my crucial DNS zones hosted there. But all the other stuff was on Namecheap's name servers. I'll probably continue with that setup, but just make sure my TTL is set fairly high.
- sparagi 13y agoWe 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.
- zargon 13y agoIf 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.
- sparagi 13y agoIf you use Route 53, your zone file is still at Namecheap (registrar). Doesn't that still make Namecheap a failure point?
- daigoba66 13y agoNo. 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".
- deleted 13y ago[deleted]
- sparagi 13y agoBut, 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?
- colmmacc 13y agoNo, 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.
- jgrahamc 13y agoYou can use CloudFlare's free plan as DNS-only.
- eli 13y agoIt makes me nervous to rely on something that's a side benefit of a free service. That said, I've heard Cloudflare's DNS network is faster than many paid alternatives.
- cobrabyte 13y agoWe've been stoked with DNSimple.
- daigoba66 13y agoInstead of putting all of your eggs in (yet another) one basket, for a site with critical availability requirements I would distribute DNS over multiple providers. If any one provider goes down it is less likely to hurt overall site availability.
- avb 13y agoYes, multiple DNS providers should be the way to go.
- blissofbeing 13y agoDNSMadeEasy, I just posted about them in this thread: https://news.ycombinator.com/item?id=7275538 https://news.ycombinator.com/item?id=7275538
- derwiki 13y agoIs there any point in freaking out or do we just have to wait this one out?
- tinco 13y agoIf it's absolutely critical that your users get service right now, it might be a good idea to at least prepare a migration to other DNS servers, like perhaps those of Linode. If the situation doesn't improve within an hour or so, it might be that they don't have a good way to deal with it, and the outtage might take long, depending on the depth of the DDoSers pockets.
- tinco 13y agoWeird, I haven't researched DNS as well as I should have. I always lived under the impression that there was this extensive DNS cache network where intermediaries responded to queries with cached results from root DNS servers. Instead, the second that this DDos hits is the second we have websites stopping working. How is it that in this day and age we can't have distributed caches of DNS entries at our providers of full dns databases. I mean there can't be more than like a few billion dns entries in the world total, which fits easily in a modern desktop computers RAM. If that is an underestimate, I can't believe a single modern server wouldn't be able to mirror the world's DNS queries for at least a providers worth of users.
- jschuur 13y agoDepends on the TTL (time to live) settings for the DNS entries, doesn't it?
- tinco 13y agoYes, perhaps there lies our folly. It's the choice between being flexible in ability to move our servers really quick, or being tolerant of DNS servers going down. I sort of hoped that a DNS client would just use an expired DNS result in case the servers would not respond, but perhaps that is naieve/dumb.
- toomuchtodo 13y ago> I sort of hoped that a DNS client would just use an expired DNS result in case the servers would not respond This would break the whole concept of TTLs. > but perhaps that is naieve/dumb. Not at all. Hard problems are hard to solve.
- MichaelTieso 13y agoThat would explain why I'm getting a massive amount of tickets from my clients why their site is down.
- kennhardy 13y agoDown for me as well. Lost access to absolutely all of my company's services. TTL 60...
- ted0 13y agoWe 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
- derwiki 13y agoThanks for posting here!
- sprouticus 13y agoThanks for the update, guys.
- nubela 13y agoYes please, thank you :) All my domains are down now but I understand how shitty (the panic!) it feels to have things going down. I'll be checking this.
- ChrisDiNicolas 13y agoGood luck guys!
- jik 13y agoJust 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.
- kennhardy 13y agoLike!
- backspaces 13y agoNot having separate status hosting is liken not salting passwords. As a NC user, I may leave just for this reason
- 13y ago
- deleted 13y ago[deleted]
- motoford 13y agoIf your site is down and you are on v2, Switch to v1. It only takes a minute and it works.
- julianc 13y agoI switched and it's the same, still down.
- motoford 13y agoAt first I thought the same. I went in to edit records, and I hit save. I checked again and it was working. I assumed there was just a delay of a minute or so and that clicking save was a coincidence. My domain is on v1 now and its still working.
- eli 13y agoWell even if you switch to a different (working) nameserver, the old nameserver will still be cached all over the place so it will still appear down for many people.
- jsm386 13y agoYeah - at least right now this worked for me. Thank you for the tip!
- plasma 13y agoHow would one add (say) AWS Route53 as a secondary DNS? I assume you'd make sure the DNS records are the same in both DNS portals; and then add Route53 as 3rd & 4th nameservers with the first and second still being Namecheap?
- IgorPartola 13y agoYes, or just switch completely to Route53.
- wes-exp 13y agoIt seems like secondary DNS is not supported, but you can change your primary DNS with the "Transfer DNS to Webhost" option.
- srik 13y agoThis is so embarrassing for me. We just put out our school computer group's website up and boom - murphys law.
- kennhardy 13y agoMay this have been a problem lasting for a week? I am monitoring a few servers with DNS records. And the last week I have found all the servers unresponsive (by DNS, not tried directly) from time to time. And after an extensive amount of troubleshooting I am unable to find a problem.
- naiyt 13y agoBest of luck to their support team. Outages can make tech support's life miserable. If you call in, just remember the person on the other side of the phone has likely been yelled at all morning for something that wasn't their fault. Totally reasonable to be upset at the situation, just don't take it out on the tech you're talking to!
- User7 13y agoJob security ;).. j/k! I imagine it must not be fun
- User7 13y agoI don't know how this website works, but I can't see the latest posts at the top of the page! I'm looking for the latest info on the issue. Are you up and running? Should I move back to v2? Thanks
- hmart 13y agoIf you're affected, you can switch your domains to their DNSv1. Seems pretty quick for most people. Via https://news.ycombinator.com/user?id=edwhitesell https://news.ycombinator.com/user?id=edwhitesell
- blissofbeing 13y agoI recently switched most of my domains to DNSMadeEasy because they are constantly in the top for speed[1], provide a top tier anycast network and for what you get are a great value. If you want speed and readability I suggest switching to a paid DNS provider. 1: http://www.solvedns.com/dns-comparison/2014/01 http://www.solvedns.com/dns-comparison/2014/01 BTW I'm not in any way affiliated, just like the service.