Hosting Private and Public Hosted Zones in Route53

Answer - C.

This is mentioned in the AWS documentation.

You can use Amazon Route 53 to configure split-view DNS, also known as split-horizon DNS.

If you want to maintain internal and external versions of the same website or application (for example, for testing changes before you make them public), you can configure public and private hosted zones to return different internal and external IP addresses for the same domain name.

Just create a public hosted zone and a private hosted zone that have the same domain name, and create the same subdomains in both hosted zones.

For more information on split view DNS, please refer to the below URL:

The correct answer is option D: Create one hosted zone with both the private and public option.

Route53 is a highly scalable and available Domain Name System (DNS) service offered by Amazon Web Services (AWS). It allows you to manage your domain names, translate domain names into IP addresses, and route Internet traffic to the appropriate resources.

When you create a hosted zone in Route53, you can choose whether to create it as a public or private hosted zone. A public hosted zone is used to route traffic on the Internet, while a private hosted zone is used to route traffic within a virtual private cloud (VPC).

In this scenario, you need to host both a private and public hosted zone for the same domain name in Route53. This can be achieved by creating a single hosted zone with both the private and public options selected.

To create a hosted zone with both private and public options, follow these steps:

1. Sign in to the AWS Management Console and navigate to the Route53 dashboard.
2. Click on the "Create Hosted Zone" button.
3. Enter the domain name you want to use for your hosted zone and select the "Public and Private Hosted Zone" option.
4. Choose the VPC(s) that you want to associate with your private hosted zone.
5. Click on the "Create" button.

Once the hosted zone is created, you can add resource records to it that are specific to each zone. For example, you could create a resource record that points to a public IP address for your public hosted zone and a resource record that points to a private IP address for your private hosted zone.

Option A is incorrect because it is possible to create both a private and public hosted zone in Route53.

Option B is incorrect because it suggests creating different resource records in the same hosted zone, but this would not separate the public and private zones.

Option C is incorrect because split-view DNS is not a feature of Route53. Split-view DNS is a method of configuring DNS servers to serve different sets of DNS information to different clients based on their location or access rights.