PTR recrod vs 'A' record with remove email sending limitation

Question

Hi, I purchased a domain from aws and created a hosted zone on route53 and a sub-domain like 'email.mydomain.com' and point to a lightsail instance's static ip as 'A' record. Then my request for reverse dns and removal of email sending limitation was completed as well as other spf, dkim and dmarc. And now I am confusing do I still need to create another hosted zone with a PTR record in it for my mail server instance in lightsail like what I saw here : https://aws.amazon.com/premiumsupport/knowledge-center/route-53-reverse-dns/?  
  
Are these two steps (reverse dns and remove email sending limit request from aws support) and (manually create new hosted zone and create PTR record inside) the samething? Like both actually giving the same effect? Or I must complete both steps so my email won't go to email receiver's spam.  
  
And is it the same using static ip with instance in lightsail vs elastic ip on aws? I know there are pricing different but what about effect?  
  
Thanks.  
  
Edited by: twhouz on May 20, 2019 11:20 PM

Answer

If you've created the A record pointing to your static IP, and Amazon has created the PTR record that points your IP to the A record's name, you should be all set.

Answer

I'm having a lot of confusion with this as well. How does this work with a Lightsail Instance I have gotten SMTP approval for? I've tried getting amazon to add a PTR on their end, but they tell me I have to an elastic IP and set up my PTR there. As I understand it, Elastic IPs only apply to EC2 Instances. How would I attach a lightsail instance to such?

PTR recrod vs 'A' record with remove email sending limitation

Conteúdo relevante