eNom Data Center Migration Mistakenly Knocks Sites Offline (bleepingcomputer.com) 21
New submitter bolind writes: A data center migration from eNom web hosting provider caused unexpected domain resolution problems that are expected to last for a few hours. Customers started to complain that they could no longer access their websites and emails due to Domain Name System (DNS) issues. My google apps gmail is not getting email, turns out DNS is not working because @enom is doing "a datacenter move" that ran into problems. What medieval times are these when a datacenter move brings down DNS for organizations? Advance warning would have been nice @enomsupport.
So That... (Score:3)
Re: So That... (Score:2)
Re: (Score:3)
They probably forgot to lower the TTLs weeks prior to the move :) It happens all the time when people move sites and change IP. Don't forget to lower your TTLs in advance if you ever do that. There is no button to flush all and every DNS server cache in the world.
Re: (Score:2)
They probably forgot to lower the TTLs weeks prior to the move :) It happens all the time when people move sites and change IP. Don't forget to lower your TTLs in advance if you ever do that. There is no button to flush all and every DNS server cache in the world.
My thought as well. Anybody with some real experience and expertise regarding DNS would have known that though. If you do not do it, not only will other DNS servers keep reporting the old IP, they may also cache resolution errors later. This whole thing has the stink of incompetence.
Re: (Score:1)
Medieval times (Score:2)
"Why the f*** is DNS down again" - King George III.
Yeah some how I don't associated DNS problems with a time when humans didn't have electricity.
Re: (Score:2)
SNAFU was still SNAFU even in medieval times, though :)
Re: (Score:2)
Well unless you were a literal king I think the entire age could be called as one big SNAFU :-)
Re: Medieval times (Score:2)
Re: (Score:3)
Honestly no idea. It's the only name I could come up with. I was thinking back to everything I knew about medieval times and the only thing I came up with was King Radovid, then I thought shit that's a character from the Witcher series. So let's go with Emperor Emhyr, ... no that's still the Witcher. Surely there must be some history in there somewhere. Ha King Baratheon. Fuck that was Game of Thrones...
George sounded like a pretty cool name. I hope he was actually a king.
This is the 21st century (Score:2)
What medieval times are these when a datacenter move brings down DNS for organizations?
Short of physical destruction of equipment [bbc.com] or the finding of some unknown flaw which is then exploited, there is no reason we should have things like this happen. The same goes for "upgrades" to mail clients by Microsoft, Google, Apple, et al. There is no reason for mail not to work after a change of software. Then again, if these same companies would stop fiddling with what isn't broken, this wouldn't be an issue.
We've
Re: (Score:2)
We've had enough experience with these systems at this point we shouldn't have to hear about screws up like this.
Well, maybe you and me and some other people have. But a lot of IT people have no clue how things actually work and if the tiniest thing goes wrong they do not know what to do. And they do not know how to make things resilient and robust either, because that requires actually knowing how thing really work as well. This thing has "Cheap" "experts" at work written all over it, which in turn means incompetent people in management that hired them.
DNS is not hard to understand. Sure, some of its aspects are tric
How does you DNS go down? (Score:2)
Are all your DNS servers on one system? On one subnet? It's one of the cheapest services to host. Now if you forgot to renew your domain it may explain it but a server/datacenter migration should not. You can setup a free tier AWS instance which means it isn't even a cost factor.
Re: How does you DNS go down? (Score:2)
Re: (Score:2)
DNS does not "go down" usually. What it does it resolves to the wrong IP or does not resolve at all, for example by caching an error.
Advance notice (Score:2)
FWIW, we *did* get notice of the data center move; fortunately, we have our own nameservers and they are both physically and topologically distant from each other...
Mine died (Score:2)
Like many others, my system went down because of this. I didn't get to pick enom, google picked it for me 12 years ago when I signed up for business email and domain.
For nearly 3 days my email was down, my main website was down, and VPN was down (in the middle of a f*cking snow storm).
The emails I did received once I notified them, were frankly embarrassing. There own internal systems were down because of a 'data center' migration for the first two days. Then they reported everything was perfect. Then they
Re: (Score:2)
Basically just the usual gross incompetence you find everywhere in IT these days. And very likely quite a few of those incompetents will soon start looking for apologies why it is not the people that messed up that are responsible. (I agree. They should never have been hired for their jobs.)
Not "medieval" times (Score:2)
Just people that do not understand what they are doing. You know, "cheap" people hired by clueless bean-counters.