|
Starting in the present day, Amazon Route 53 Resolver helps utilizing the DNS over HTTPS (DoH) protocol for each inbound and outbound Resolver endpoints. As the title suggests, DoH helps HTTP or HTTP/2 over TLS to encrypt the information exchanged for Domain Name System (DNS) resolutions.
Using TLS encryption, DoH will increase privateness and safety by stopping eavesdropping and manipulation of DNS knowledge 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. Using DoH additionally helps comply with suggestions equivalent to these described in this memorandum of the US Office of Management and Budget (OMB).
DNS over HTTPS assist in Amazon Route 53 Resolver
You can 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 achieve this, you may 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 may 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, whenever you create or replace an inbound or outbound Resolver endpoint, you may 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 information.
- Both, 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 observe.
Using DNS over HTTPS with Amazon Route 53 Resolver
In 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 possibility.
After that, I configure the IP addresses for DNS queries. I choose two Availability Zones and, for every, a subnet. For this setup, I exploit the choice to have the IP addresses robotically chosen from these accessible 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.
Similarly, 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 purchasers 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.
Things to know
DNS over HTTPS assist for Amazon Route 53 Resolver is out there in the present day in all AWS Regions the place Route 53 Resolver is obtainable, together with GovCloud Regions and Regions based mostly in China.
DNS over port 53 continues to be the default for inbound or outbound Resolver endpoints. In this fashion, you don’t must replace your present automation tooling except you need to undertake DNS over HTTPS.
There is not any further price for utilizing DNS over HTTPS with Resolver endpoints. For extra info, see Route 53 pricing.
— Danilo