Hi, everyone, and welcome back.
Now, in today's video, we are going to discuss about the Route 53 resolver endpoints.
Now, in the earlier video associated with hybrid DNS, we looked into how the resolver endpoint can
replace the custom DNS server vs easy to instance for the overall resolution from the private hosted
zone.
So in today's video, first, we are going to have a quick demo to understand on how this setup works
post, which will be discussing things in more detail.
Now as we were discussing that the EC two instance from the VPC number two, which is paired with a
VPC number one that in turn is associated with the private hosted zone, is not able to resolve the
overall record by sending the query to the plus two IP address.
So in such cases you can make use of the root 2 to 3 resolver endpoints.
Now for today's video, I already have the endpoint that is set up.
Let me quickly show you.
So we have one inbound endpoint that is available.
And if you look into this endpoint, there are two set of IP addresses associated with this.
So in order to connect to the endpoint, there are two set of addresses on premise whenever it wants
to make a query at a root 53 level, it needs to send the DNS query to one of these set of IP addresses.
So let's go ahead and try it out.
I'll copy one of the address here and let's replace this.
And you see the oral resolution is working.
Now, this one 7231 0.5 associated with zero one demo dot internal if you'd like to see let's also verify
from the hosted zone.
So our demo dot internal hosted zone has this 01. demo dot internal record with 170 to 31 0.5.
All right.
So I hope with this at a high level overview, you understood the benefits that the endpoint provides.
Now, when we discuss about the type of endpoints, there are two primary types.
One is the inbound resolver endpoint and second one is the outbound resolver endpoint.
Now the use cases that we were discussing were related to the inbound resolver endpoint where some kind
of a server from on premise or the PID.
VPC wants to go ahead and resolve the record of Route 53 private hosted zone.
And in a similar way, when we discuss about the endpoints here, you have an inbound endpoint and you
have the outbound endpoint that you can see.
And for today's demo, we had taken an example of the inbound endpoints.
Now for today's video at a very high level overview, let's go ahead and understand both about the inbound
as well as the outbound endpoints and the use cases that it covers.
Now, first, that we already know that the inbound resolver endpoints allows the DNS queries to your
VPC from ON-PREMISE network or another VPC.
This is something that we have seen.
On the contrary, the outbound resolver endpoints allows the DNS query from your VPC to on premise network
or another VPC.
So this can be understood with the diagram.
Again, this is taken directly from the documentation so that even while you're going through the docs,
it becomes easier to revise.
Now if you look into this diagram, there are two separate infrastructure here.
One is the on premise data center on the left and you have a VPC on the right.
Now, when we discuss about the inbound resolver endpoints, this dashed line that you see over here,
this is associated with inbound and the solid line that you see over here, this is associated with
the outbound resolver endpoint.
So at the overview, let's go ahead and quickly look into the workflow.
So there is a client computer in the on premise data center that wants to resolve the records that are
part of the Route 53.
It can be a private hosted zone.
So what it will do first, it will send a query to the DNS resolver associated with the on premise data
center.
Now the on premise DNS resolver through a connection, it can be a VPN connection, just for an example
is sending the traffic to the inbound endpoint.
Now we know that inbound endpoint has a specific set of IP address which is configured at a dense resolver
level at the on premise data center.
So from the DNS of the on premise data center, the query is made to the inbound endpoint.
From the inbound endpoint, the traffic goes to the VPC plus to address and then it goes to the Route
53 resolver.
Now, again, note that this DNS resolver is optional.
Client can also directly send the request to the inbound endpoint, and the workflow remains to be the
same.
So this is one easy part that we have already seen.
The second one that we're discussing is the outbound resolver.
So in this case, what happens is that the DNS zone is hosted in the on premise data center, for an
example.
It is not at a Route 53 level and the EC two instance in the VPC wants to perform the resolution of
the record that is hosted in the DNS server of the on premise data center.
So in such case, the EC two instance will go ahead and send the query to the VPC plus two address,
which is associated with the resolver.
Now this resolver through the outbound endpoint sends the query to the DNS server of the on premise.
And from here the record is fetched and it is sent back to the EC2 instance.
So this solves both the use cases where the records are hosted at a Route 53 level or the records are
hosted at a DNS server in the on premise data center, or maybe in a different kind of infrastructure.
So this is a very high level overview about the Route 53 resolver endpoints, and with this will conclude
today's video.