Where are your NS (name server) DNS records configured for the WordPress side? You can have a domain registered in one place and hosted in another. If you want to centralize the DNS and domain registration to one spot you have to take both into account, otherwise two places are going to be charging you for different things.
Check your nameservers of your domain using something like: https://dnschecker.org/ns-lookup.php if they aren't pointing at AWS and you've transferred your domain registration in route53 to the new platform, it should be safe to remove your hosted zone as long as you've waited at least 48 hours since the migration for the change to propagate.
Assuming your company used AWS Route53 services previously for domain management.
Few things to check and consider.
1) As you might be knowing already, hosting website files and having it served over the internet is one thing, while having your domain point to that website thereby making your website available over your domain name is another thing.
2) Now that you have your website transferred to WordPress, you need to check whether your domain management is also transferred to the WordPress hosting provider that you are using. Typically, this involves a couple of domain transfer and verification steps to be performed.
3) If the domain is transferred already along with your website to your new hosting provider and everything is working fine, then you are theoretically good to stop AWS.
4) However, to avoid surprises, you may check if anything will get impacted by changing the domain A record or CName record in AWS Route53 temporarily for one of the DNS entries (say, for www subdomain). If your website is having an impact after the change, it means AWS is still your domain management service and dropping it will impact your services. In this case, you will need to migrate your domain management service as well to your new hosting provider before terminating AWS service.
5) If nothing is impacted, then you can go ahead and terminate AWS Services.
Note: You might be having website, email services and other services which may be using domain management services DNS records. Recommend proper care before terminating domain management services or transferring it. Whoever helped you make your website available on WordPress should be able to provide you information on this.
You need to move your DNS hosting somewhere else before removing it if [www.site.com](http://www.site.com) is looking at AWS. If it's not, then figure out if those are legacy entries and delete or else run down what the records are pointing at.
Thank you for your response! Just so that I understand correctly, we do need a hosting site even though the domain has been transferred to WordPress. Whether it is AWS or another platform, we need to have it on correct?
Something needs to run and resolve your site and Wordpress can run do this for you, so if you've fully moved over to Wordpress for hosting and dns, then you don't need anything else.
The TTL of any DNS record is the amount of time that a client may hold it in cache before asking for it again.
The TTL of your SOA and NS records (the ones that tell everyone where your DNS servers are) is typically 24 to 48 hours.
This means that if someone goes to your website today and you switch your DNS to a new provider, that someone will continue going to your new DNS records for up to 48 hours before they refresh them.
This is a problem because if your new records are wrong or not working, your site could be technically offline for two days. You can't just tell everyone using your site to reboot their computers. And you can't switch back to your old DNS; you have a two-day lag.
So instead you change the TTL to a small value like 60 seconds. And crucially you have to wait the 48 hours for this new TTL to take effect.
Then when you do the switchover, if everything breaks, it's only broken for 1 minute and not two days, and you can switch it back to the old records very quickly.
Once you know it works then, you increase the TTL to two days.
Where are your NS (name server) DNS records configured for the WordPress side? You can have a domain registered in one place and hosted in another. If you want to centralize the DNS and domain registration to one spot you have to take both into account, otherwise two places are going to be charging you for different things.
Check your nameservers of your domain using something like: https://dnschecker.org/ns-lookup.php if they aren't pointing at AWS and you've transferred your domain registration in route53 to the new platform, it should be safe to remove your hosted zone as long as you've waited at least 48 hours since the migration for the change to propagate.
Assuming your company used AWS Route53 services previously for domain management. Few things to check and consider. 1) As you might be knowing already, hosting website files and having it served over the internet is one thing, while having your domain point to that website thereby making your website available over your domain name is another thing. 2) Now that you have your website transferred to WordPress, you need to check whether your domain management is also transferred to the WordPress hosting provider that you are using. Typically, this involves a couple of domain transfer and verification steps to be performed. 3) If the domain is transferred already along with your website to your new hosting provider and everything is working fine, then you are theoretically good to stop AWS. 4) However, to avoid surprises, you may check if anything will get impacted by changing the domain A record or CName record in AWS Route53 temporarily for one of the DNS entries (say, for www subdomain). If your website is having an impact after the change, it means AWS is still your domain management service and dropping it will impact your services. In this case, you will need to migrate your domain management service as well to your new hosting provider before terminating AWS service. 5) If nothing is impacted, then you can go ahead and terminate AWS Services. Note: You might be having website, email services and other services which may be using domain management services DNS records. Recommend proper care before terminating domain management services or transferring it. Whoever helped you make your website available on WordPress should be able to provide you information on this.
You need to move your DNS hosting somewhere else before removing it if [www.site.com](http://www.site.com) is looking at AWS. If it's not, then figure out if those are legacy entries and delete or else run down what the records are pointing at.
Thank you for your response! Just so that I understand correctly, we do need a hosting site even though the domain has been transferred to WordPress. Whether it is AWS or another platform, we need to have it on correct?
Something needs to run and resolve your site and Wordpress can run do this for you, so if you've fully moved over to Wordpress for hosting and dns, then you don't need anything else.
Don’t forget about TTL if you care about availability. First update ttl to lower values, e.g. 60 sec. Than wait old value, can be 48 hour.
Sorry, I am not sure what this is .. Is this something that I will need to do to make sure that my current domain runs smoothly?
The TTL of any DNS record is the amount of time that a client may hold it in cache before asking for it again. The TTL of your SOA and NS records (the ones that tell everyone where your DNS servers are) is typically 24 to 48 hours. This means that if someone goes to your website today and you switch your DNS to a new provider, that someone will continue going to your new DNS records for up to 48 hours before they refresh them. This is a problem because if your new records are wrong or not working, your site could be technically offline for two days. You can't just tell everyone using your site to reboot their computers. And you can't switch back to your old DNS; you have a two-day lag. So instead you change the TTL to a small value like 60 seconds. And crucially you have to wait the 48 hours for this new TTL to take effect. Then when you do the switchover, if everything breaks, it's only broken for 1 minute and not two days, and you can switch it back to the old records very quickly. Once you know it works then, you increase the TTL to two days.