I have recently transferred my domain name trademarklawexplained.com from One.com to AWS.
I have the following set-up in Route53:
For some reason, none of my records (SOA, NS and A) have had any effect. trademarklawexplained.com does not map to 35.176.22.92, nor does it even look at the name server (I tested it with this tool)
Have I set up my hosted zone incorrectly, should I somehow publish it, or is the issue with One.com?
If someone could point me in the right direction to troubleshoot it would be greatly appreciated.
Figured it out in the end…
For a name server to be associated with a Route53 hosted zone, do the following:
- Create a Hosted zone for your domain name. Note the NS record.
- Go to Registered Domains > example.com > Add or edit name servers > Add the name servers from step 1.
When transferring a domain to AWS, it keeps the old NS record. Make sure to change it as per step 2.
Checking the records it is still pointing to old records.
You need to update the DNS servers with your domain registrar for it to take effect.
If the DNS servers are updated, you might need to wait for the TTL time defined with the previous registrar to expire. DNS servers can cache those records until that TTL time defined in those NS records.
How long have you waited? DNS records have a TTL (Time To Live). DNS servers around the world will cache your domain records until the TTL expires. For example, in your screenshot the TTL for your Name Servers is 172800 seconds which is 48 hours. In general it takes two or three days for the Internet to start caching your new domain records, sometimes longer. If it has been more than a week, then there is a problem.
来源：https://stackoverflow.com/questions/46435715/dns-hosted-zone-not-taking-effect-aws-route53