@Adam I just noticed we can't connect to QUIC.Cloud using CF integration.
I need to enter this record:
CNAME @ pointing to c31533.tier1.quicns.com
I think this is CNAME flattening as mentioned by @AdamM
So it's going to be hard for clients to connect to Quic.Cloud.
I am now left with Cloudflare but not simple to configure dynamic page caching on a CF free plan.
Can you help me understand quickly how can we set up an out of the box CDN easy for our customers to use?
That would help me. Thank you.
I would like to see a Quic.cloud DNS integration the same way you've done it with CF.