Confusion about QUIC Cloud CDN

  • Resolved 9itish

    (@9itish)


    4 years, 8 months ago

    Hi,

    I was recently trying to set up QUIC.cloud CDN service for one of my websites by following this guide: https://docs.litespeedtech.com/products/lscdn/onboarding/

    These are my Cloudflare DNS records: https://i.imgur.com/XvvS6XI.png

    Content of the image:

    
CNAME www domain.com
A origin HOST.SERVER.IP
CNAME domain.com cxxx.tier1.quic.cloud

    My website is loading properly after setting everything up. The QUIC.cloud dashboard says that my CNAME is verified as well.

    However, I still don’t understand what is the role of “A” record here which points to the server IP.

    These is a screenshot of the DNS checker tool: https://i.imgur.com/KsbRIVd.png

    1. Can I remove the origin A record?
    2. Do I need to add any other record here as well?

    The DNS record images on the onboarding page are a little confusing because they show different records in each image.

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    When you have QC CDN set up , it will be like this :

    user access your domian.com —> domain resolve to cxxxx.tier1.quic.cloud , our CDN node will then serve cached page or reverse proxy to your backend if not cached.

    in your screenshot , both root domain and www domain are on CNAME now , that’s what QC needed , all other A records are not matter to QC, but only for your own usage.

    2. no , but please try make both www and root domain to cxxxx.tier1.quic.cloud CNAME

    Best regards,

    Thread Starter 9itish

    (@9itish)

    Thanks @qtwrk for the clarification. ??

    1. “all other A records are not matter to QC, but only for your own usage.” So, does this mean that I can remove the origin record?

    I thought it was important because it was included in the onboarding tutorial. (https://docs.litespeedtech.com/products/lscdn/onboarding/).

    2. So, my DNS records should be for QUIC.cloud should both point to cxxx.tier1.quic.cloud?

    
CNAME www cxxx.tier1.quic.cloud
CNAME domain.com cxxx.tier1.quic.cloud

    I have one more question.

    People say that using CDN reduces server load. What does it mean?

    1. Does this mean it only reduces bandwidth load.
    2. Does it reduce all server load like CPU usage, RAM and Bandwidth.

    When pages are loaded from the QUIC.cloud cache, is there no communication between my webhost server and client computer?

    Thanks.

    • This reply was modified 4 years, 8 months ago by 9itish.
    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    1, if you have no use for that “origin” , yes

    2. ideally yes , but if you only use www or root domain for your site , this step is optinal

    yes , that’s how CDN does

    basically , without CDN

    user <—> your server

    with CDN

    user <—> CDN <—> your server

    when resources is already cached on CDN , there is no need to reach your server again , therefore , reduce the resource usage.

    1. Does this mean it only reduces bandwidth load.
    2. Does it reduce all server load like CPU usage, RAM and Bandwidth.

    that depends , for QC , as we can cache dynamic pages as well , so both bandwidth and CPU/RAM can be reduced , for conventional CDN which only caches static resources , it only saves bandwidth (though serve static files also uses CPU/RAM , but it’s minimal usage.)

    When pages are loaded from the QUIC.cloud cache, is there no communication between my webhost server and client computer?

    ideally , yes , when both dynamic page and static resources are cached properly , no communication to your server.

    Best regards,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Confusion about QUIC Cloud CDN’ is closed to new replies.