Hayden, and welcome back.
In today's video, we'll be discussing about the multivolume value and routing now the multivolume answer
routing basically allows us to return multiple values so these multiple values can be IP addresses in
response to a specific DNS query.
Now, one great feature associated with the multi value answer routing is that it allows us to check
the health of the sources so that the Road 53 can respond with details of only healthy resources.
Now, again, this might be a little confusing and listen, and they'll go good and have a demo.
So let's jump to the practical section and look into how exactly the multivolume set out.
So within myself, if I quickly do a nice lookup on my day, Modot believes that Internet you will see
that it is basically returning for recordset.
So you have IP address 10 Seventy-Seven 036, then you have 037.
You have zeroed out it and you have zero Lotfy.
So for one specific domain you have multiple values which are being redone now.
This is referred to as the multivolume answer routing.
So let's look into how exactly it might look like and 53.
So this is way the three console now within my hosting two and you see I have four records.
Now each of these records has the same domain, which is my damanaki believes that Internet.
However, each one of them has a different set of IP addresses.
So no, if I just open up one of them in the right hand side, if you look into the routing policy,
the routing policy is of multi value answer.
So that basically means that any time I'd be in a server request for the domain of my demo that believes
that internal multiple servers, IP addresses would be sent in the DNS response.
Now, this type of policy helps.
Let's say you have a lot of Web servers and if let's say you want to distribute the traffic, then you
can make use of multi value routing policy.
Now, again, this is not a replacement to the elastic load balancer.
However, I hope at a high level what we you got an understanding on what exactly this is.
Now, if you look into the PBT, in the second point, we were discussing that multi value and the routing
allows us to take the help of the resources.
So it might happen, let's say that these are for Web servers.
Now, among these four Web servers, one of them is not working.
And what we want is that any time a DNS request comes for the domain of my damanaki believes that indent
and then they're out, 53 should only serve the IP addresses associated with the Web servers whose heritage
has been passed.
It should not serve.
The IP addresses of the service has failed the health check, so that can be associated with the hatake.
So this multi value unsearched you can associate with the heritage that you create within the road 53.
So this is a great feature.
So let me quickly show you and how exactly you can create a multi value answer based routing.
So let's see alkalis.
Let's call it as a multivolume.
I will give it the value of 190 to 168 10.1.
Now within the routing policy, I'll call it as a multi value answer and I'll give it the idea of one.
Now, you can also associate it with a heretic.
Now for the simplicity.
Since you're starting studying multi value, I'll just set this as default in the array, so I'll go
ahead and I create a recordset.
So this is the first recordset.
Let's create one Murekatete, I'll name it multivolume.
Make sure you name this same.
The value would be 192 168.
Tendered to the routing policy again would be multi value answer.
The basic idea would be to.
In a similar case, we'll do one more, let's name this the multivolume as a 190 to 168, 10 three.
And I'll put the idea of three and I'll go ahead and I created all eight.
So now there are three records which are part of the multi value answer now or within the easy to insist.
Let's go ahead and do it and look up.
I'll say multi value dot com labs or Internet.
And I see it basically responded back with a three IP addresses associated with the record set of multi
value that keep the Internet.
Now, one important part to remember is that if you do not associate your multi value routing policy
with the Help Desk, so if you see all the heritage are being determined as no.
So in this case, about 50 trevitt assume that all of these IP addresses are held.
And whenever a DNS query is being made similar to what we had done, whenever DNS query is being made,
about 53 will respond with all the IP addresses.
All right.
So, again, if you do not associate the multi value routing policy with any help, check it out.
53 will assume all the hosts are to be healthy and it will return the IP addresses of all the records
associated with that specific routing policy in case if you associate it with the health check and if
the heretic does not succeed, then the Route 53 will not send the IP address of the record whose health
check has been filled.
So this is the high level overview about the multi value and the routing.
One last point to remember is that about 53 and respond up to DNS query with up to eight health records.
So this is one important part to remember.
So this will conclude this video, I hope, at a high level or of you you got the understanding on what
multivolume value and routing policy is all about, that this will conclude this.
We do.
I hope this video has been informative for you.
And I look forward to see you in the next video.