The difference between ALIAS and CNAME and when to use them

The chief distinction between a CNAME report and an ALIAS report shouldn’t be within the outcome—each level to a different DNS record—however in how they resolve the goal DNS report when queried. Because of this distinction, one is protected to make use of on the zone apex (for instance, bare area similar to instance.com), whereas the opposite shouldn’t be.

Let’s begin with the CNAME report sort. It merely factors a DNS title, like www.instance.com, at one other DNS title, like lb.instance.web.  This tells the resolver to lookup the reply on the reference title for all DNS sorts (for instance, A, AAAA, MX, NS, SOA, and others). This introduces a efficiency penalty, since not less than one further DNS lookup have to be carried out to resolve the goal (lb.instance.web). Within the case of neither report ever having been queried earlier than by your recursive resolver, it’s much more costly timewise, as the complete DNS hierarchy could also be traversed for each data:

1. You because the DNS shopper (or stub resolver) question your recursive resolver for www.instance.com.
2. Your recursive resolver queries the foundation title server for www.instance.com.
3. The foundation title server refers your recursive resolver to the .com Prime-Stage Area (TLD) authoritative server.
4. Your recursive resolver queries the .com TLD authoritative server for www.instance.com.
5. The .com TLD authoritative server refers your recursive server to the authoritative servers for instance.com.
6. Your recursive resolver queries the authoritative servers for www.instance.com and receives lb.instance.web as the reply.
7. Your recursive resolver caches the reply and returns it to you.
8. You now subject a second question to your recursive resolver for lb.instance.web.
9. Your recursive resolver queries the foundation title server for lb.instance.web.
10. The foundation title server refers your recursive resolver to the .web Prime-Stage Area (TLD) authoritative server.
11. Your recursive resolver queries the .web TLD authoritative server for lb.instance.web.
12. The .web TLD authoritative server refers your recursive server to the authoritative servers for instance.web.
13. Your recursive resolver queries the authoritative servers for lb.instance.web and receives an IP handle as the reply.
14. Your recursive resolver caches the reply and returns it to you.

Every of those steps consumes not less than a number of milliseconds, typically extra, relying on community situations. This may add as much as a substantial period of time that you just spend ready for the ultimate, actionable reply of an IP handle.

Within the case of an ALIAS report, all the identical actions are taken as with the CNAME, besides the authoritative server for instance.com performs steps six by means of 13 for you and returns the ultimate reply as each an IPv4 and IPv6 handle. This affords two benefits and one important downside:

Benefits

Sooner ultimate reply decision pace

Typically, the authoritative servers for instance.com can have the reply cached and thus can return the reply in a short time.

The alias response will probably be A and AAAA data. Since an ALIAS report returns the reply that contains a number of IP addresses, it may be used wherever an A or AAAA report can be utilized—together with the zone apex. This makes it extra versatile than a CNAME, which can’t be used on the zone apex.  The flexibleness of the Alias report is required when your website is posted on a number of the hottest CDNs that require using CNAME data in order for you your customers to have the ability to entry it by way of the bare area similar to instance.com.

Disadvantages

Geotargeting info is misplaced

Since it’s the authoritative server for instance.com that’s issuing the queries for lb.instance.web, then any clever routing performance on the lb.instance.web report will act upon the placement of the authoritative server, not in your location. The EDNS0 edns-client-subnet choice doesn’t apply right here. This implies that you could be be doubtlessly mis-routed: for instance, in case you are in New York and the authoritative server for instance.com is in California, then lb.instance.com will consider you to be in California and can return a solution that’s distinctly sub-optimal for you in New York.  Nevertheless, in case you are utilizing a DNS supplier with worldwide pops, then it’s seemingly that the authoritative DNS server will probably be positioned in your area, thus mitigating this subject.

One essential factor to notice is that NS1 collapses CNAME data, offered that all of them fall inside the NS1 system. NS1’s nameservers are authoritative for each the CNAME and the goal report. Collapsing merely signifies that the NS1 nameserver will return the complete chain of data, from CNAME to ultimate reply, in a single response. This eliminates all the extra lookup steps and permits you to use CNAME data, even in a nested configuration, with none efficiency penalty.

And even higher, NS1 helps a novel report sort known as a Linked Report. That is principally a symbolic hyperlink inside our platform that acts as an ALIAS report may, besides with sub-microsecond decision pace. To make use of a Linked Report, merely create the goal report as you normally would (it may be of any sort) after which create a second report to level to it and choose the Linked Report choice. Observe that Linked Information can cross area (zone) boundaries and even account boundaries inside NS1 and provide a strong solution to set up and optimize your DNS report construction.

CNAME, ALIAS and Linked Report Reference Chart

INSERT DISPLAY TEXT HERE