Bird
0
0

You set an MX record in Route 53 but emails are not received. What is a common DNS mistake causing this?

medium📝 Debug Q14 of 15
AWS - Route 53
You set an MX record in Route 53 but emails are not received. What is a common DNS mistake causing this?
AUsing an A record instead of MX for mail routing.
BUsing a CNAME record for the mail server instead of MX.
CSetting the MX record with a trailing dot missing in the domain name.
DSetting TTL to zero for the MX record.
Step-by-Step Solution
Solution:

  1. Step 1: Check MX record format

    MX records require fully qualified domain names ending with a dot to be valid.

  2. Step 2: Identify common error

    Missing trailing dot causes DNS to treat the name as relative, breaking mail routing.

  3. Final Answer:

    Setting the MX record with a trailing dot missing in the domain name. -> Option C

  4. Quick Check:

    MX domain needs trailing dot [OK]
Quick Trick: MX domain names must end with a dot in DNS records [OK]
Common Mistakes:
  • Using A record for mail routing
  • Omitting trailing dot in MX domain
  • Confusing CNAME with MX record

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
Architecture Best Practices - Multi-tier architecture patterns - Quiz 7medium Architecture Best Practices - Why AWS Well-Architected matters - Quiz 5medium Cost Optimization - Budgets and cost anomaly detection - Quiz 4medium Cost Optimization - Spot Instances for cost savings - Quiz 9hard ECS and Fargate - Why container services matter on AWS - Quiz 2easy ECS and Fargate - ECS service auto scaling - Quiz 13medium ECS and Fargate - ECR for container image registry - Quiz 6medium Route 53 - Failover routing for disaster recovery - Quiz 9hard Serverless Architecture - Serverless vs container decision - Quiz 9hard Serverless Architecture - Cognito for user authentication - Quiz 5medium