I am using the Amazon Route 53 DNS service and my SMTP server cannot receive email from clients after I created a mail exchanger (MX) record for my SMTP server in Route 53.

If the public hosted zone that you configure for the Route 53 DNS service is not populated with the appropriate resource record sets or if your domain name registrar does not point to the name servers in your Route 53 public hosted zone, clients cannot connect to your SMTP server.

  1. Review Values that You Specify When You Create or Edit Amazon Route 53 Resource Record Sets to ensure that you have created the appropriate resource record sets for your SMTP server. At a minimum, the public hosted zone must contain a mail exchanger (MX) record for your SMTP server as described at Values for Basic Resource Record Sets.
  2. If you are using a domain name registrar other than Route 53, verify that your domain name registrar is referencing the name servers in your Route 53 public hosted zone. To do this, query an Internet-based whois utility such as the InterNIC Whois Search web page to do the following:
    • Find the registrar for your domain name - Enter your domain name in the query field, select the Domain option, and then choose Submit. The query results should list the domain name registrar as well as the authoritative name servers for the domain name.
      Note
      If the query results return a list of name servers other than the name servers associated with your Route 53 public hosted zone, DNS queries for your SMTP server will not be sent to Route 53, and you must contact your domain name registrar to update the list of name servers associated with your domain name.
    • Find contact information for your domain registrar - Enter the name of the registrar in the query field, select the Registrar option, and then choose Submit. Use this information to contact your domain registrar and request that they update the list of name servers for your domain name to reference the name servers in the Route 53 public hosted zone for your domain.
    • Verify that the DNS service you are switching from does not delete any resource record sets for your domain before the TTL on the registrars name servers expires. This can take 48 hours or more, and Route 53 DNS services will not respond to DNS queries for a domain name until the TTL period for the domain name server records has elapsed. For more information, see Waiting for Your Changes to Take Effect.
  3. If you are using Route 53 as your domain registrar, ensure that clients can access the resource record sets in your Route 53 public hosted zone(s). For more information, see How do I verify that resource record sets in an Amazon Route 53 public hosted zone are accessible from the Internet?, which provides an example scenario for testing client access to an MX record.
    Note
    Some DNS providers require that you prepend ‘@’ to an MX record set name or simply create an MX record set with the name ‘@’ when creating an MX record set for a root domain. Route 53 MX record set names should not be prepended with ‘@’ or any other character. If you want to create an MX record set for a root domain in Route 53, leave the record set name blank and provide appropriate values for the remaining fields of the Route 53 MX record set.
  4. If the MX record has been configured correctly and your SMTP server is still unable to receive email, contact your email service provider for further investigation.

Amazon Route 53, hosted zone, domain, create, transfer, name server, change, email, MX, registrar, SMTP


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center.