If you’re using your own on-premises SMTP server with its own public IP address, and you want Route 53 to respond to reverse DNS lookup queries for that IP address, create a public hosted zone and put the PTR record there. In the steps that follow, we use the example IP address 192.168.1.2.

In this example, the following values would be provided to the ISP for this purpose:

Depending on the time to live (TTL) of the previous NS record, which may be cached in end-user local DNS servers, it will take some time for this new setup to take effect.

If example.com has multiple IP blocks, you must create additional reverse hosted zones with corresponding PTR records that you want your IP addresses to be resolved to.

If you're using Elastic IP addresses for your servers, create an A resource record set that points to the correct Elastic IP address, and use the Request to Remove Email Sending Limitations form. Make sure to specify each domain name and the corresponding Elastic IP address. Note that a valid forward DNS record pointing to an existing Elastic IP address must exist before a corresponding PTR record can be created.

If you're using non-AWS resources and your IP addresses belong to a third party (for example, another cloud service), use the method provided by the owner of your IP addresses to configure reverse DNS. In some cases, the owner of the IP addresses will have to set up reverse DNS for you. In addition, use the method provided by the domain registrar to update the domain with the name servers for the Route 53 hosted zone.