upvote

points

by finaard23 hours ago |
comments
upvoteby somewhatgoated23 hours ago|
next
[-]
I don’t get your point, what is the weird thing?

That he is complaining about his email being down or that he trusted AWS at all with email?

reply
upvoteby rkent23 hours ago|
parent|
[-]
The only way that email is down for days for a competent sysadmin is if their DNS is also with AWS, so I assumed that was the case. Assuming that is true, what is weird to me is that, after deciding he hated AWS and left it, that he still kept his business DNS (the most important service there is) with AWS.
reply
upvoteby hluska22 hours ago|
parent|
[-]
If you would have read the article, you would know that the writer had DNS hosted at AWS, would have read why he made that choice and would know of his plans to migrate off.
reply
upvoteby finaard21 hours ago|
parent|
[-]
I assumed he just had DNS at AWS, but after re-reading I guess he has DNS _and_ domain registrations at AWS, which would be a special kind of stupid. That's something we were advising customers against already back when cloud wasn't a thing yet to enable fast transfers when stuff goes south

(to clarify: DNS+domain at the same service can be OK, as long as you have nothing else there. As soon as you start having other stuff, keep the DNS there, but move the domain registration away. Depending on which domain make sure you have auth keys, access to the admin domain or whatever would enable moving the domain without registrar cooperation. In my hosting days I did my fair share of emergency transfers and infrastructure to help companies get their basics online again after a SNAFU - totally doable to have first mail coming in again within a working day)

reply
upvoteby panny23 hours ago|
prev|
[-]
>new servers would be online somewhere else within hours of it going down

Yeah, no that's not how it works with email. You have to build reputation for weeks or receivers throttle you.

reply
upvoteby kassner21 hours ago|
parent|
next
[-]
It is pretty much unacceptable to have a domain bouncing emails, so I’d be out of the provider before the MX TTL even expires.

For outgoing emails, reputation is a huge issue, but at the same time it’s also fairly trivial to set up a (different) 3rd-party (gmail, outlook, sendgrid, whatever) with previous reputation so you can get back communicating.

reply
upvoteby finaard22 hours ago|
parent|
prev|
[-]
I'm not running a spam business. I've been operating my own mailservers (and related infrastructure) for more than 25 years now, without issues.
reply