The difference between ALIAS and CNAME and when to use them

The chief distinction between a CNAME document and an ALIAS document will not be within the end result—each level to a different DNS record—however in how they resolve the goal DNS document when queried. Because of this distinction, one is secure to make use of on the zone apex (for instance, bare area comparable to instance.com), whereas the opposite will not be.

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

1. You because the DNS shopper (or stub resolver) question your recursive resolver for www.instance.com.
2. Your recursive resolver queries the basis identify server for www.instance.com.
3. The foundation identify server refers your recursive resolver to the .com High-Degree 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 difficulty a second question to your recursive resolver for lb.instance.web.
9. Your recursive resolver queries the basis identify server for lb.instance.web.
10. The foundation identify server refers your recursive resolver to the .web High-Degree 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 tackle as the reply.
14. Your recursive resolver caches the reply and returns it to you.

Every of those steps consumes at the least a number of milliseconds, typically extra, relying on community situations. This could add as much as a substantial period of time that you just spend ready for the ultimate, actionable reply of an IP tackle.

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

Benefits

Quicker ultimate reply decision pace

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

The alias response will probably be A and AAAA information. Since an ALIAS document returns the reply that includes a number of IP addresses, it may be used wherever an A or AAAA document 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 pliability of the Alias document is required when your web site is posted on a number of the hottest CDNs that require the usage of CNAME information if you’d like your customers to have the ability to entry it through the bare area comparable to instance.com.

Disadvantages

Geotargeting data 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 document will act upon the situation of the authoritative server, not in your location. The EDNS0 edns-client-subnet possibility doesn’t apply right here. This implies that you could be be doubtlessly mis-routed: for instance, if you’re 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, if you’re utilizing a DNS supplier with worldwide pops, then it’s possible that the authoritative DNS server will probably be positioned in your area, thus mitigating this difficulty.

One necessary factor to notice is that NS1 collapses CNAME information, offered that all of them fall throughout the NS1 system. NS1’s nameservers are authoritative for each the CNAME and the goal document. Collapsing merely implies that the NS1 nameserver will return the total chain of information, from CNAME to ultimate reply, in a single response. This eliminates all the extra lookup steps and means that you can use CNAME information, even in a nested configuration, with none efficiency penalty.

And even higher, NS1 helps a singular document kind referred to as a Linked Document. That is mainly a symbolic hyperlink inside our platform that acts as an ALIAS document may, besides with sub-microsecond decision pace. To make use of a Linked Document, merely create the goal document as you normally would (it may be of any kind) after which create a second document to level to it and choose the Linked Document possibility. Notice that Linked Information can cross area (zone) boundaries and even account boundaries inside NS1 and supply a strong solution to arrange and optimize your DNS document construction.

CNAME, ALIAS and Linked Document Reference Chart

INSERT DISPLAY TEXT HERE