Amazon SES & Email Deliverability
Application mail that arrives, with bounces handled before they cost you the account.
From $299 2–4 days
A zone moved with every record accounted for, and the TTLs lowered before the change rather than after.
From $199
Typically $199–$399, fixed in writing before anything starts.
What moves it up
Some of this you can check yourself, right now, for free: DNS Health Check →
The zone gets rebuilt by hand at the new provider and about ninety per cent of it is correct, because the records people remember are the ones that serve web pages. What goes missing is everything that is not a website: the SPF record, the DKIM selector, and the verification TXT for some service that will keep working for weeks and then quietly stop. And because nobody lowered the TTL first, the mistake is cached for a day — so the fix, when it comes, is also invisible for a day.
dig +noall +answer @<current-nameserver> <domain> ANY — and every record type separately, because ANY is often refusedA record-by-record diff of the exported zone against what was created at the destinationdig +trace <domain> from outside the network, confirming delegation rather than a cached answerThe TTL on every record lowered and allowed to expire BEFORE the nameserver change, not during itYes, if the old zone is left serving until the new one is confirmed. Both sets of nameservers answer identically for the overlap, so it does not matter which a resolver reaches. What causes outages is deleting the old zone the same afternoon.
No, and usually you should not do both at once. Nameservers and registrar are separate things — you can point a domain registered anywhere at Route 53. Doing both in one change means an outage has two possible causes.
It is about fifty cents a month per zone plus queries, and for most domains that is a rounding error. What you get for it is health checks, alias records that track an AWS resource without a hardcoded IP, and an API — none of which a free registrar DNS panel offers.
The nameserver delegation itself is governed by the TLD's TTL, typically a day or two, which is why the old zone stays up. Individual records inside the zone move at whatever TTL you set, which is why they get lowered first.
Application mail that arrives, with bounces handled before they cost you the account.
From $299 2–4 days
Moved onto AWS with the cutover rehearsed, the DNS planned, and the old host still standing.
From $459 2–5 days
Tell me what you are running and I will come back with a fixed price and a date. If it turns out you do not need this, I will say that instead.
Prefer to talk? Book a free call ↗ · Or hire me on Upwork ↗ · Typical reply within one business day.
Sunday to Thursday, 09:00–18:00 EET. Outside that I will still look, but I will not promise a time.
One person, one time zone. If round-the-clock cover is what you need, you need a team, and I will say so rather than sell you a plan that cannot deliver it.
You pay Amazon directly and you keep control of the account. Nothing here resells your infrastructure or sits between you and your own billing.
Every service page lists exactly what pushes a quote above it, before you ask. You get a fixed number in writing before any work begins.