Hacker News new | ask | show | jobs
by walrus01 2879 days ago
I would start by:

a) buying my own domain

b) ensuring that the authoritative ns1/ns2/ns3 records for that domain are hosted at a diverse set of geographically diverse nameservers, for example an ns1 that you run and then using route53 and another non-route53-service for authoritative slaves.

c) setting the MX records for it to either a mail server that you run, or a third party mail server. This is sort of a compromise approach. You can use office365 or google if you don't want to fully host your own mail. You say you don't want to deal with the hassle of mail deliverability, so use either of those and let them handle the spam filtering, SPF and DKIM. Mail that's hosted by office365 is trusted by just about everything out there, in terms of not having other peoples' SMTP daemons reject or blackhole your mail. If either of those cuts you off for some arbitrary reason in the future, you at least have the ability to change the MX records to another service as you see fit.