I have a site hosted at AWS, domain name is set at AWS Route 53.
I want to move to hosting to another host, linode, and keeping AWS Route 53.
I just made a clone of original site to the new host, and works fine. As last thing, I changed settings (in AWS routing) as:
myexample.com
A
XX.XXX.XXX.XX #changed to new IP
myexample.com
NS
ns-734.awsdns-12.net.
ns-36.awsdns-42.com.
ns-762.awsdns-60.org.
ns-143.awsdns-32.co.uk.
myexample.com.
SOA
ns-574.awsdns-21.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
But the new site yield error 403 (while it works from its IP).
The new host has server configured to use server_name as "myexample.com" , so it should not be a problem at server side, but at routing.
What am doing wrong? Do I really move also the routing dns to the new host? I would like to keep using AWS S3, and so leave SOA and NS records.