1. Home
  2. Docs
  3. CDN
  4. Configuring DNS
  5. QUIC.cloud DNS vs. CNAME Records

QUIC.cloud DNS vs. CNAME Records

When you enable QUIC.cloud CDN, you are asked to choose a method of connecting the CDN to your domain:

  • QUIC.cloud DNS
  • CNAME
  • Cloudflare

Let’s look at what each of these options entails.

QUIC.cloud DNS

If you want to use QUIC.cloud with a root (or apex) domain such as example.com, then QUIC.cloud DNS is your easiest option. (Note, though, that a root domain is not required. You can use QUIC.cloud DNS with your www domain [like www.example.com], or any other subdomain [such as blogging-is-cool.example.com] that you wish.)

QUIC.cloud DNS was built specifically for our CDN, which means it well integrated into our service, and is easily accessible from your QUIC.cloud dashboard, if you ever need to change your configuration.

CNAME and QUIC.cloud DNS

As we will discuss in a moment below, QUIC.cloud assigns you a CNAME. This is meant to be used with an external DNS provider, so if you decide to go with QUIC.cloud DNS, you can ignore the CNAME value we provide. There is no need to switch your A record to the assigned CNAME record when you use QUIC.cloud DNS.

CNAME

You can keep your current DNS provider and simply add a CNAME record with the domain assigned to you by QUIC.cloud (it should look something like c12345.tier1.quicns.com).

If you wish to use QUIC.cloud with your root domain (example.com), your DNS provider must offer CNAME flattening, or ANAME/ALIAS records. Many DNS providers do not support these options, and in that case you have two options:

  1. Switch to QUIC.cloud DNS, or some other provider who offers ANAME or ALIAS records.
  2. Change your website to a www domain or other subdomain and keep your current DNS provider.

Cloudflare

If you are switching over from Cloudflare, you can keep your DNS there if you wish. Just make sure that the little cloud icon in your Cloudflare configuration is gray instead of orange.

Was this article helpful to you? Yes No