CDNs use DNS to steer traffic to edge networks. Dig can confirm whether a domain is pointing at the CDN, but it does not test CDN cache or origin health.

Useful dig commands

dig www.example.com CNAME
dig example.com A
dig example.com AAAA

Troubleshooting checklist

  1. Check CNAME or A records based on the CDN instructions.
  2. Compare root and www hostnames.
  3. Look for stale records from a previous provider.
  4. Move to CDN dashboard and HTTP headers after DNS is correct.

How to interpret the result

If the answer matches the expected value, DNS is probably not the layer causing the current symptom. Continue with HTTP, TLS, mail server, firewall, or application checks. If the answer is missing, stale, or different between resolvers, keep the investigation in DNS until the public answer is correct.

Support note

When opening a ticket with a DNS provider, include the exact name, record type, resolver tested, returned value, and time of the lookup. That is much more useful than saying “DNS is not working.”