3 ms·
All of my websites using Rackspace DNS where down for around 9 hours. It was not a good start on a Monday. And it was even harder to explain that your websites
by dubcanada 12y ago
All of my websites using Rackspace DNS where down for around 9 hours.
It was not a good start on a Monday. And it was even harder to explain that your websites are up, but not up to a client lol, and there is basically nothing I can do.
So yah this marks the point at which I will be using R53 and RS DNS servers.
- colmmacc 12y agoTip: If you're using >=2 providers to survive DDOS attacks, it's best to use no more than two name servers from any one provider. That's because resolvers will generally try up to 3 different name servers before giving up. The "no more than two nameservers" rule means that those attempts will always span at least two providers.
- dubcanada 12y agoAmazon by default gives 4 nameservers, can you only use two?
- rustyconover 12y agoSure you can.
- jasoncartwright 12y agoI didn't know that. Do you have any more info, or a link to some docs that show this?
- bluedino 12y agoSites on Rackspace servers, DNS through NetSol (not that they are good or bad, but it wasn't RS). Didn't realize anything was going on until seeing this article.
- pbhjpbhj 12y ago>but not up to a client lol // Why don't DNS clients fail back to use the most recent good IP address as a default? Indeed how can I set up my Kubuntu desktop to have this behaviour. Most domains probably point to the same IP for years at a time I'd imagine. If that's true it seems very strange that just because example.com's DNS server was offline this one day out of the last 600 that my browser can't "guess" that "123.45.67.89 example.com" is going to work. You'd need to add some security around that to avoid abuse I'm sure but doesn't it seem reasonable? Shouldn't DNS failures only prevent you from getting to a server if the IP has changed??