And welcome back into this video we'll be discussing about the geolocation crowding now, as the name
suggests, geolocation crowding allows us to choose the resources based on the geographic location of
the users.
So basically, this can be understood with a simple example.
So let's say that you might want all the queries from the initial location.
So all the DNA sequences which are originating from the location to be related to the elastic load balancer
in the Singapore region.
Similarly, if you have the query, which is from the U.S., then you might want to direct those queries
to the North Virginia region.
So all of those configurations can be achieved with the help of geolocation routing.
So let me quickly show you a quick demo on how exactly this might work before we discuss some of the
important pointers.
So this is made out of the three console.
Now, within my Zune, there are two records.
Now, both of these records has the same name, which is my demo that believes that Internet.
However, they have different IP addresses.
One has the IP address of ten seventy seven, five or 10 and second and 77.
Fighter 20.
Now if you look into the routing policy where you get the routing policy is of type geolocation and
within a year we have actually specified the location as the United States and we have given the idea
of two.
Similarly, in the other recordset we have the location of India and the idea of one.
So basically from Seelie, I am actually logged into a two instance in the North Virginia region here.
If we quickly do it and look up on my demo DARD Capi Labrada Internet, you will see that the recordset
which has been sent in the response is 2077 seven 20.
Now, this is the reason why, because for the record set of 10, 77, five or 20, we have the location
set as United States.
You, in fact, have one more record set of 10, 77, five or ten.
But this will be solved only when the location is India.
So this type of geolocation based routing is quite useful.
So many times it has been observed.
I'm sure you also might have observed that whenever you visit a website, you might get a message that
the contents of this website are not visible for your country.
So that can be easily achieved with the help of geolocation.
You can also achieve it at a personal level, like at the Ingenix level.
That can also be possible.
But to the road 53, it is much more simpler now in case if you want to create a geolocation based routing,
it is very simple.
So you create a record set, you can give it a name.
Let's say I'll give it the name of geolocation.
You can give it a value as 1877, five or 30.
Now, the routing policy you can select here as geolocation and within the location you can specify
by continent.
So Africa, Antarctica, Asia, Europe, North America, Oceania, South America.
All right.
So you can specify by continent you can even specify a country.
So this is the granularity which the geo location based routing policy supports.
Now, there are certain important considerations that you should remember before you go ahead and implement
your location routing within your production environment.
The first is the dual location routing works by mapping the database to the IP addresses.
Now, in such cases of mapping, the results are not always accurate.
Now, the reason is because there might be certain Internet service providers that might not have any
geolocation data which is associated with them.
Or it can happen that some ISPs might move that IP block to a different country without notification.
So in such cases, you might get an issue.
So for such cases, around 53 allows us to have a default resource block associated with the geo location
based routing policy.
So let me quickly show you that.
So within the location, if you go up, there is a block of default.
So this is the default block.
So in case if you get DNS query from ISP, which is not matching any of the content and yes, it does
happen.
So in such cases, you want to handle that in an appropriate manner.
So for such cases you can have the location of default and then you can specify one of the IP addresses
depending upon the use case that your organization might have.
So this does happen.
I would not say it is very common, but you need to make sure that if you are implementing geolocation,
make sure you also have the reservation for the default location.
So this is the high level overview about the geo location based routing policy.
I hope this video has been informative for you.
And I look forward to see you in the next video.