No MX Records for Apprunner App using Hosted Zone

0

I recently migrated to AWS services and am running a web app in an App Runner instance and my domain registar is Rebel. I've changed my NS records on Rebel to point to the hosted zone created in Route53 and have added all the necessary records to my hosted zone and waited for TTL to expire. I don't seem to have any MX records when I dig and my emails are bouncing.

Any help would be appreciated

1 Answer
0

When migrating your domain to AWS Route 53 and encountering issues with MX records and email delivery, here are some steps to troubleshoot the problem:

  1. Verify MX Records: Double-check the MX records you have configured in the hosted zone in Route 53. Ensure that they are correctly set up with the appropriate values, including the priority and the destination email server's fully qualified domain name (FQDN).

  2. TTL (Time to Live): After making changes to DNS records, it's important to wait for the TTL (Time to Live) value to expire. TTL determines how long DNS resolvers cache the records. Ensure that you have waited for the old TTL duration to pass to allow the changes to propagate.

  3. DNS Propagation: Check if the DNS changes have propagated globally. You can use online DNS propagation checking tools to verify if the MX records have propagated to the necessary DNS servers worldwide.

  4. DNS Resolution: Ensure that your domain is resolving to the correct nameservers. You can use tools like dig or online DNS lookup tools to query the nameservers associated with your domain. Confirm that the nameservers listed match the ones provided by Route 53.

  5. MX Record Lookup: Perform an MX record lookup using tools like dig or online MX record lookup tools to check if the MX records are correctly set up and accessible globally. This will help identify any discrepancies or issues with the MX records.

  6. Email Server Configuration: Verify that the email server you are using is correctly configured to receive emails for your domain. Ensure that the email server is properly set up to handle incoming emails and that it is accessible and functioning correctly.

If you have followed these steps and are still experiencing issues with MX records and email delivery, it is recommended to reach out to AWS Support for further assistance. They can help investigate the specific configuration of your Route 53 hosted zone and provide guidance to resolve the MX record and email delivery issues.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions