Beginning right this moment, Amazon Route 53 Resolver helps utilizing the DNS over HTTPS (DoH) protocol for each inbound and outbound Resolver endpoints. Because the title suggests, DoH helps HTTP or HTTP/2 over TLS to encrypt the info exchanged for Area Identify System (DNS) resolutions.

Utilizing TLS encryption, DoH will increase privateness and safety by stopping eavesdropping and manipulation of DNS information as it’s exchanged between a DoH consumer and the DoH-based DNS resolver.

This helps you implement a zero-trust structure the place no actor, system, community, or service working outdoors or inside your safety perimeter is trusted and all community site visitors is encrypted. Utilizing DoH additionally helps observe suggestions similar to these described in this memorandum of the US Workplace of Administration and Finances (OMB).

DNS over HTTPS help in Amazon Route 53 Resolver
You should use Amazon Route 53 Resolver to resolve DNS queries in hybrid cloud environments. For instance, it permits AWS providers entry for DNS requests from anyplace inside your hybrid community. To take action, you’ll be able to arrange inbound and outbound Resolver endpoints:

• Inbound Resolver endpoints permit DNS queries to your VPC out of your on-premises community or one other VPC.
• Outbound Resolver endpoints permit DNS queries out of your VPC to your on-premises community or one other VPC.

After you configure the Resolver endpoints, you’ll be able to arrange guidelines that specify the title of the domains for which you need to ahead DNS queries out of your VPC to an on-premises DNS resolver (outbound) and from on-premises to your VPC (inbound).

Now, while you create or replace an inbound or outbound Resolver endpoint, you’ll be able to specify which protocols to make use of:

• DNS over port 53 (Do53), which is utilizing both UDP or TCP to ship the packets.
• DNS over HTTPS (DoH), which is utilizing TLS to encrypt the info.
• Each, relying on which one is utilized by the DNS consumer.
• For FIPS compliance, there’s a particular implementation (DoH-FIPS) for inbound endpoints.

Let’s see how this works in follow.

Utilizing DNS over HTTPS with Amazon Route 53 Resolver
Within the Route 53 console, I select Inbound endpoints from the Resolver part of the navigation pane. There, I select Create inbound endpoint.

I enter a reputation for the endpoint, choose the VPC, the safety group, and the endpoint kind (IPv4, IPv6, or dual-stack). To permit utilizing each encrypted and unencrypted DNS resolutions, I choose Do53, DoH, and DoH-FIPS within the Protocols for this endpoint choice.

After that, I configure the IP addresses for DNS queries. I choose two Availability Zones and, for every, a subnet. For this setup, I take advantage of the choice to have the IP addresses mechanically chosen from these out there within the subnet.

After I full the creation of the inbound endpoint, I configure the DNS server in my community to ahead requests for the amazonaws.com area (utilized by AWS service endpoints) to the inbound endpoint IP addresses.

Equally, I create an outbound Resolver endpoint and and choose each Do53 and DoH as protocols. Then, I create forwarding guidelines that inform for which domains the outbound Resolver endpoint ought to ahead requests to the DNS servers in my community.

Now, when the DNS shoppers in my hybrid atmosphere use DNS over HTTPS of their requests, DNS resolutions are encrypted. Optionally, I can implement encryption and choose solely DoH within the configuration of inbound and outbound endpoints.

Issues to know
DNS over HTTPS help for Amazon Route 53 Resolver is accessible right this moment in all AWS Areas the place Route 53 Resolver is obtainable, together with GovCloud Areas and Areas based mostly in China.

DNS over port 53 continues to be the default for inbound or outbound Resolver endpoints. On this approach, you don’t have to replace your present automation tooling except you need to undertake DNS over HTTPS.

There is no such thing as a further value for utilizing DNS over HTTPS with Resolver endpoints. For extra data, see Route 53 pricing.

Begin utilizing DNS over HTTPS with Amazon Route 53 Resolver to extend privateness and safety on your hybrid cloud environments.

— Danilo