CNAME record chaining can simplify IP address management and cloud integration, but often at the expense of webpage load time.
A Canonical Name (CNAME) is a DNS record that enables the creation of an alias from one domain name to another. This approach eliminates the need for every domain name to have its own IP address, which eases management and creates a single point for third-party services to integrate with cloud platforms.
The downside of CNAME record chaining – when one CNAME record points to another – is that it creates latency. Instead of directing a user directly from a domain name to an IP address, a chain creates multiple DNS lookups along the way. This latency can increase web page load time, which hurts the user experience and can even lead to lost revenue.
Oracle Dyn will host a free webinar Tuesday, June 5 to help organizations deal with webpage load time issues and other problems associated with CNAME chaining. In the webinar, Scott Taylor, director of solutions engineering, will explain exactly how much CNAME record chaining hurts performance, and he’ll describe how a distributed DNS can reduce those effects.
The webinar will also feature a case study about a retail company that used Oracle Dyn DNS and a content delivery network to avoid a large CNAME record chain and improve its webpage load time. Click here to register for the event, “Three Things You Probably Didn’t Know About CNAMES, But Should.”