Forwarding inbound DNS queries to your VPCs - Amazon Route 53

Forwarding inbound DNS queries to your VPCs

To forward DNS queries from your network to Resolver, you create an inbound endpoint. An inbound endpoint specifies the IP addresses (from the range of IP addresses available to your VPC) that you want DNS resolvers on your network to forward DNS queries to. Those IP addresses aren't public IP addresses, so for each inbound endpoint, you need to connect your VPC to your network using either an AWS Direct Connect connection or a VPN connection.

Configuring inbound forwarding

To create an inbound endpoint, perform the following procedure.

To create an inbound endpoint
  1. Sign in to the AWS Management Console and open the Route 53 console at https://console.aws.amazon.com/route53/.

  2. In the navigation pane, choose Inbound endpoints.

  3. On the navigation bar, choose the Region where you want to create an inbound endpoint.

  4. Choose Create inbound endpoint.

  5. Enter the applicable values. For more information, see Values that you specify when you create or edit inbound endpoints.

  6. Choose Create.

  7. Configure DNS resolvers on your network to forward the applicable DNS queries to the IP addresses for your inbound endpoint. For more information, refer to the documentation for your DNS application.

Values that you specify when you create or edit inbound endpoints

When you create or edit an inbound endpoint, you specify the following values:

Outpost ID

If you are creating the endpoint for a Resolver on an AWS Outposts VPC, this is the AWS Outposts ID.

Endpoint name

A friendly name that lets you easily find an inbound endpoint on the dashboard.

VPC in the region-name Region

All inbound DNS queries from your network pass through this VPC on the way to Resolver.

Security group for this endpoint

The ID of one or more security groups that you want to use to control access to this VPC. The security group that you specify must include one or more inbound rules. Inbound rules must allow TCP and UDP access on port 53. You can't change this value after you create the endpoint.

Some security group rules will cause your connection to be tracked and the overall maximum queries per second per IP address for an inbound endpoint can be as low as 1500. To avoid connection tracking caused by a security group, see Untracked connections.

Note

In order to add multiple security groups, use the AWS CLI command create-resolver-endpoint. For more information, see create-resolver-endpoint

For more information, see Security groups for your VPC in the Amazon VPC User Guide.

Endpoint type

The endpoint type can be either IPv4, IPv6, or dual-stack IP addresses. For a dual-stack endpoint, the endpoint will have both IPv4 and IPv6 address that your DNS resolver on your network can forward DNS query to.

IP addresses

The IP addresses that you want DNS resolvers on your network to forward DNS queries to. We require you to specify a minimum of two IP addresses for redundancy. Note the following:

Multiple Availability Zones

We recommend that you specify IP addresses in at least two Availability Zones. You can optionally specify additional IP addresses in those or other Availability Zones.

IP addresses and Amazon VPC elastic network interfaces

For each combination of Availability Zone, Subnet, and IP address that you specify, Resolver creates an Amazon VPC elastic network interface. For the current maximum number of DNS queries per second per IP address in an endpoint, see Quotas on Route 53 Resolver. For information about pricing for each elastic network interface, see "Amazon Route 53" on the Amazon Route 53 pricing page.

Note

Resolver endpoint has a private IP address. These IP addresses will not change through the course of an endpoint's life.

For each IP address, specify the following values. Each IP address must be in an Availability Zone in the VPC that you specified in VPC in the region-name Region.

Availability Zone

The Availability Zone that you want DNS queries to pass through on the way to your VPC. The Availability Zone that you specify must be configured with a subnet.

Subnet

The subnet that contains the IP address that you want to forward DNS queries to. The subnet must have an available IP address.

The subnet IP address must match the Endpoint type.

IP address

The IP address that you want to forward DNS queries to.

Choose whether you want Resolver to choose an IP address for you from among the available IP addresses in the specified subnet, or you want to specify the IP address yourself.

If you choose to specify the IP address yourself, enter either an IPv4 or IPv6 address.

Protocols

Endpoint protocol determines how data is transmitted to the inbound endpoint. Choose a protocol, or protocols, depending on the level of security needed.

  • Do53: (Default) The data is relayed using the Route 53 Resolver without additional encryption. While the data cannot be read by external parties, it can be viewed within the AWS networks.

  • DoH: The data is transmitted over an encrypted HTTPS session. DoH adds an added level of security where data can't be decrypted by unauthorized users, and can't be read by anyone except the intended recipient.

  • DoH-FIPS: The data is transmitted over an encrypted HTTPS session that is compliant with the FIPS 140-2 cryptographic standard. Supported for inbound endpoints only. For more information, see FIPS PUB 140-2.

For an inbound endpoint you can apply the protocols as follows:

  • Do53 and DoH in combination.

  • Do53 and DoH-FIPS in combination.

  • Do53 alone.

  • DoH alone.

  • DoH-FIPS alone.

  • None, which is treated as Do53.

Important

You can't change the protocol of an inbound endpoint directly from only Do53 to only DoH, or DoH-FIPS. This is to prevent a sudden disruption to incoming traffic that relies on Do53. To change the protocol from Do53 to DoH, or DoH-FIPS, you must first enable both Do53 and DoH, or Do53 and DoH-FIPS, to make sure that all incoming traffic has transferred to using the DoH protocol, or DoH-FIPS, and then remove the Do53.

Tags

Specify one or more keys and the corresponding values. For example, you might specify Cost center for Key and specify 456 for Value.