And welcome back into this, we will be discussing about the drought policy in drought, 53 now of the
drought in police, he basically allows us to specify the proportions in which the traffic should be
related to the underlying server.
Now, we'll understand this in the upcoming point, so let's discuss that.
So let's assume that if we want to send a small portion of the traffic to your website team, then you
can specify the date of one to 99.
So in this case, what would happen is the resource with one gets one percent of the traffic and then
gets 99 percent of the traffic.
Now, this is very useful because let's say that you have created a new team for the website.
Now, you don't really want all the 100 percent of that traffic to be sent to your and your website.
It might contain bugs.
So what do you do?
You tell that only one percent of your traffic should be sent to the new website, while the 99 percent
would still be sent to the older, stable Web site.
Now, if you get a positive feedback from the one of the traffic, then you can start to move it to
five percent, 10 percent, 20 percent of the traffic and so on.
So the way in which you can tell that all that one percent data traffic should be sent is based on weight.
So you assign a weight to each recordset.
Now, the formula is the weight of a specific record by the sum of weight of all the records which are
part of that specific record set.
So let me quickly show how exactly this might look like.
So it is made out of detection.
So if you see I have two record sets which are available.
One is we take out Zelboraf, Darkon, and it has about 54 or 30.
And again, you have the same record, which is a way to deliver that outcome, which has this set of
128 today to know within this record set, if you look into the routing policy, the routing policies
we did and the weight years to now for the other one, you're the lead is one.
Now, depending upon the weight that you assign to each and every record take, the amount of traffic
that will be sent across that domain will vary.
So let me quickly show you, if I quickly do a day, the first second set is 128, the second date,
the record set is 128.
The third time the record set is fifty four thirty.
So you see the traffic is being doubted depending upon the.
We now do make sure that if you create a drought and if you are testing it within these two incidents,
the traffic might not draw primarily because of the DNS cache.
So that is one important part to remember.
Now let me quickly show you how you can create a that I didn't.
So let's say I call it as they move it.
No, you can give it a new value, let's say 54 or 28 or 54 or 20.
And the routing policy, you can select it as we do now.
Novo, you can specify the wait.
Let me specify the weight of two and the you can just give out a random ID and say twice.
Now, you can also specify that let's put it at zero and create the record set in a similar way.
I create one more recordset, make sure you give the same name, which is then move it.
Let's give it the name of one twenty seven or zero zero.
That one again, this would be of type Radik the way it would be one.
And certainly you can give the name that you intend to give it a detail of zero seconds and I'll do
it.
Create.
I think now there are two record set now, each record set as a different way, as we discussed in your
testimony, specifically, if you're doing it within your easy two instance, you might not see the
records to be altered according to the beat, primarily because of their DNA sketch.
So let me do one thing.
I used the record to move it and it gave the response of 54.
Now, if you're wondering what this is, so this is basically the name server, which is NSA and 187.
So if you look over here, you have NSA run 187.
So this is the name server that we are getting to.
So now next time you did a query, it said two one two seven zero zero.
And so you see the traffic is being routed to multiple records set.
Now, before we conclude this, we do.
There is one important point that you should remember.
And the point is that if you want to stop sending traffic to the resource, you can change the weight
of that specific recordset to zero.
So in this way, the traffic would be stopped sending to those specific resources.
So this is the high level overview about the data records set in around 52.
I hope this video has been informative for you.
And I look forward to see you in the next video.