![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
DNS change today
Hi all,
We had a brief outage this morning. The cause was an (unexpected) policy change by our DNS provider, Dyn, deciding to shut us off. They had to roll back the change for unrelated reasons so we were back online, but it does mean that we need to migrate off of their service.
ETA: The policy change was that, for about 10 years now -- as long as I've been using Dyn! -- they had no usage/quota limits on their DNS service. Given that DNS requests are tiny and easy to serve, this made sense. They made a business decision recently to establish some (rather tiny) quotas. We're ... quite in excess of them (by some 15,000%) and we don't want to pay in excess of $500 USD/month for DNS service. Amazon's price is 10% of that. They probably tried to contact us, but I don't recall seeing any emails. Anyway, that's it; it's nothing particularly nefarious.
We will be moving our DNS service to Amazon's Route53 service. This kind of migration is fairly easy technically, but if there are problems it will probably mean Dreamwidth will be offline until they can be resolved. And, given the nature of how DNS works, it means that any outage will probably be measured in hours rather than minutes.
I've done my best to ensure that the changeover will go smoothly. If anything happens, though, we'll be on our dreamwidth account to keep everybody apprised of the progress.
The switch will be flipped around 3:30pm PDT / 2230 UTC today, this is in about 90 minutes.
no subject
(Was it the fan fic? It's always the fan fic.)
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
(no subject)
no subject
EDIT: AND THEN TWO OTHER PEOPLE BEAT ME TO THE QUESTION, hahaha
no subject
no subject
no subject
(no subject)
no subject
no subject
no subject
no subject
Dyn's model is that of Enterprise. They used to offer the bare-bones service we used which was pretty cheap and had no quotas. They've tried to get us to upgrade to Enterprise before, but it's super expensive and Rolls-Royce-esque. We don't need a Rolls. I'm more a BMW guy myself. Something solid, good, reasonably cheap, and gets the job done. Actually that probably better describes a Honda.
Anyway.
So, yeah, Amazon will be lots better. They've got a long track record of how they manage their pricing -- it never goes up, if anything it can be counted on to go down. Even if it doesn't, I'd much rather a pay-per-query model that is predictable.
no subject
no subject
(ahaha we broke the internet)
no subject
no subject
The mail servers use the same DNS as the web servers. Emailed-in comments may be delayed a bit, but they should get there eventually. (Really, the best answer is 'it depends'. It couldn't hurt to save a copy of the sent mail or CC yourself, just in case.)
(no subject)
no subject
no subject
Route 53 is owned and operated by Amazon, yes. (To clarify, though: none of this involves user data in any way. DNS is the internet's phone book, essentially, keeping track of where you should go when you type a domain name into your browser's address bar -- when you type in, say, dw-maintenance.dreamwidth.org, your ISP looks at its own table and sees if it knows where that is, and if it doesn't, it calls up your DNS provider and says "yo, where do I find this address". We're switching the place that your ISP calls to find out where it finds that address.)
(no subject)
no subject
no subject
no subject
no subject
A second useful thing about it is that folks like Amazon actually have a widely distributed DNS infrastructure. Every DNS request is going to take some time to complete, which adds to how long it takes the site to load for people. If we hosted DNS ourself then our users who aren't near Texas, USA will have extra latency. Amazon has servers all over the globe and this helps the site feel faster for people who aren't near us.
Also personally, it's well worth the $50 a month to have someone else worry about DNS infrastructure. They will actually do it much better than I could in the time I have available. (And I'd rather spend that time on DW itself!)
DNS
(no subject)
(no subject)
no subject
Just sayin.
no subject
(no subject)
(no subject)
(no subject)
business practices
no subject
no subject
no subject
no subject
Back when I was working tier 1 tech support for a local domain registrar, I told my supervisor that I was reading up on DNS in order to do my job better. Of course I'd poked at zone files in college just like most of my friends, but I wanted to read up now that I'd be dealing with end-users who had probably done terrible things to their A Record. My supervisor shuddered.
"You know how you have two evil magicians battling in a room somewhere?" he asked me. I nodded. "And that stuff that falls to the floor when they're fighting?" I nodded. "That's DNS."
It's been a couple years, so I guess if I finish the new Seanan book quickly, I know what the rest of my leisure reading's going to be!
no subject
(no subject)
(no subject)
(no subject)
no subject
no subject
Cheers for letting us know, even though you got very little notice and we had less. Moving servers, hosts and what-not is no fun.
*HUGS ALL THE DW STAFF*
no subject
no subject
Edit: Well today is the 5th so it seems all went well and easy!
no subject
If you just want to check that everything is all right, we (as in .SE, the Swedish ccTLD registry) have a web interface intended for public use at http://dnscheck.iis.se/
no subject
no subject
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)