Here you are.
And welcome back.
Now, in today's video, we'll be discussing about the primary difference between a see name and an
alias record.
So at a high level overview, just for a revision, see name record basically is used for pointing a
domain name to another hostname.
For example, you have an example dot internal and you can create a name record to route the traffic
to Cape Labs dot.
So this is the basics of see name.
Now whenever you're using C name record, there are certain challenges and drawbacks that would come.
One of the most important one is that it cannot be used with the root of the domain.
For example, let's say you have example.com and you want to create a name record for this apex domain
to another host name.
It can be KP or it can be another DNS.
Then this kind of a scenario does not work with C name record.
This is very important to remember.
Now let me quickly show you this.
So currently I have a hosted zone of internal.
Let's go ahead and create a record.
So record, let's call it this demo and the record type.
Let's just call it a C name and within the value, let's us put it in.
I'll create a record.
So this is perfectly fine.
So now what you're using here is you're using a sub domain, and the sub domain is demo, dot, dot,
internal.
You are not using the apex domain, which is internal.
Now let's say what you want is anyone who is visiting the KP Labs dot internal.
The traffic should be routed to KP Labs dot in.
How do you solve that issue?
Now one of the answers that comes is you can simply create a name record.
Let's try it out.
So for Internal, let's create a C name and within the value, I'll just call it s 11.
And when you try and create a record, immediately you get an error stating that C name with DNS, KP
Labs or internal is not permitted at Apex Zone.
So this is basically the apex KP Labs internal.
So in case if you want to route the traffic of KP Labs or internal to another DNS, it can be applied
in in this case.
But in a lot of organizations you have a load balancer.
So anyone who is visiting your website, the traffic will be directed toward the load balancer.
I also have a load balancer in this case.
Let's also explore that.
So let's say anyone visiting KP Labs or Internal, the traffic should go to the load balancer as soon
as you go in and try and create a record.
Again, you basically get an issue on this.
And this is one of the drawback of the C name record.
So in order to overcome this, you basically make use of an Alias record.
So whenever you want the root domain to point to another DNS, maybe elastic load balancer is three
bucket cloud front distribution.
It will not work with C name record as we were looking into.
So to resolve this specific drawback, it provides us the Alias record which allows us to even point
the root domain to the DNS of the services.
For example, you have a example.com and you want to route the traffic towards the service DNS.
So all you have to do is you have to create a simple alias record here.
So let's explore this.
So now, instead of going ahead and selecting this record type of C name, let's use the record type
of A, I'll enable the alias here.
As soon as you enable the alias here, you have a lot of option where you can route the traffic to various
endpoints.
It can be network load balancer, VPC, endpoint cloud, front distribution and so on.
So I already have a sample load balancer available, so I'll go ahead and select Alias to application
and classic load balancer within here.
You can go ahead and select the region.
Let's say the region is us East one, so you have a US East one and then within here you can just select
the load balancer that is available.
In this case we only have one.
So once then you can go ahead and create a record.
And now, perfect.
Now you see CP Labs Internal, which is the apex domain now, is routing the traffic towards the load
balancer, DNS grid.
So I hope at a high level overview you understood the basics of see name record, the limitation of
that and also the benefits of Alias record and how important it is to go ahead and configure this in
the production environment.
So with this will conclude today's video.