What should a solutions architect do to rapidly migrate the DNS hosting service?
Create an Amazon Route 53 public hosted zone for the domain name. Import the zone file containing the domain records hosted by the previous provider.
Create an Amazon Route 53 private hosted zone for the domain name. Import the zone file containing the domain records hosted by the previous provider.
Create a Simple AD directory in AWS. Enable zone transfer between the DNS provider and AWS Directory Service for Microsoft Active Directory for the domain records.
Create an Amazon Route 53 Resolver inbound endpoint in the VPC. Specify the IP addresses that the provider’s DNS will forward DNS queries to. Configure the provider’s DNS to forward DNS queries for the domain to the IP addresses that are specified in the inbound endpoint.
Explanations:
Creating a public hosted zone in Amazon Route 53 and importing the zone file is the correct approach to migrate DNS hosting for a domain name. Route 53 supports importing existing DNS records, which allows for a smooth transition from the previous provider to AWS-managed DNS.
A private hosted zone is used for managing DNS records within a VPC, not for publicly accessible domain names. Since the company’s website is likely publicly facing, this option is not suitable.
AWS Simple AD and AWS Directory Service are designed for managing directory services (e.g., for Active Directory integration), not for DNS hosting of a public domain. This option is not applicable for migrating the DNS hosting service.
This option involves setting up a Resolver inbound endpoint, which is used for forwarding DNS queries from on-premises or external DNS servers into a VPC. However, this does not address migrating the DNS hosting for a domain name to AWS. It’s more suitable for hybrid DNS configurations and not for managing DNS records directly.