The MX record typo that routed internal emails to a parked domain
by•
Cleaned up our DNS records during a domain migration project.
Transcribed the mail exchange server host string by hand and accidentally left off a single letter in the domain suffix. The change propagated fast.
For nearly three hours, transactional emails, password reset links and automated system alerts were bouncing off an un-owned parking page before an alert finally triggered.
7 views
Replies
Password resets are the scary part of that list, because for some users mail is the login. In my app one sign in method is an emailed link, and even with DNS right, delivery can quietly lag in ways no bounce alert shows: Yahoo throttled our sending service's shared IPs, so a mail to a yahoo.com or aol.com address waited anywhere from 1 to 19 hours while Gmail got it in seconds. Hundreds of deferral retries a day, zero bounces. The alert I would want for your case and mine is not "a mail bounced" but "a sign in or reset mail took longer than a few minutes to land", per mailbox provider, because that is when people give up.