3 ms·

This happened to me with AWS somewhat recently[0], and I never found out exactly what happened. I just chalk it up to some dev made a mistake and didn't tell a

• use-net 7y ago
  cloudns.net does it a bit more customer-friendly way: they e-mailed me saying they deleted some domains not because some entries were broken or had problematic entries, but just because it was "underused", i.e. too few DNS resolve calls. So the tiny data packets in their nameserver caused them unnecessary consumption of electricity or whatever. Very compelling! This is how they do business these days. They bombarded people with all sorts of useless info, but not about this policy of theirs. Makes you feel very much like the proverbial "valued customer". Everything is going downhill in this century, that's a fact.
• jcrites 7y ago
  I've been involved in using Route 53 to manage thousands of DNS zones, and haven't come across something like that. I'd recommend putting in a support request via the account that was affected to ensure that it gets looked at. If you haven't already, you might consider checking the CloudTrail logs for the account in question to see if there were any API commands related to the zone.
  • PetahNZ 7y ago
    Although not DNS related, I have had weird things happen on AWS, such as spikes of 5xx errors reported from CloudFront which was backed by ELB/EB, but the ELB is showing no errors. Even after contacting AWS support they couldn't resolve it, said they required application logs, but there is no logs because the requests never reached the application servers.