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 an Amazon Route 53 public hosted zone allows the company to manage its domain name records directly on AWS. Importing the existing zone file from the previous provider ensures a rapid migration of DNS records, allowing for quick resolution of any service disruptions caused by the outages. This solution is suitable for public-facing websites.
A private hosted zone is designed for internal DNS resolution within an Amazon VPC and would not be suitable for a public website. Since the company’s website is externally accessible, a public hosted zone is required instead.
Creating a Simple AD directory and enabling zone transfer is not necessary for migrating DNS records to Route 53. This option does not address the requirement for a managed DNS service on AWS and does not facilitate the rapid migration of the domain records.
An Amazon Route 53 Resolver inbound endpoint is used for hybrid cloud scenarios to allow on-premises networks to forward DNS queries to Route 53. However, this option does not migrate the DNS hosting service but instead sets up query forwarding. It does not provide a direct solution for migrating DNS records to a more resilient service.