CDN with custom domains in Azure - Deep Dive

Overview - CDN with custom domains

What is it?

A Content Delivery Network (CDN) with custom domains is a service that delivers website content quickly by using servers close to users, while allowing the website to use its own domain name instead of the default CDN address. This means visitors see the website's own web address, making the experience seamless and professional. The CDN stores copies of content in many places worldwide to speed up loading times and reduce delays.

Why it matters

Without a CDN, users far from the website's main server experience slow loading times, which can cause frustration and lost visitors. Using custom domains with a CDN keeps the website's brand consistent and trustworthy, while improving speed and reliability. This combination helps businesses keep users happy and competitive online.

Where it fits

Before learning this, you should understand basic web hosting and DNS (how domain names point to servers). After this, you can explore advanced CDN features like security with HTTPS, caching rules, and integration with other cloud services.

Mental Model

Core Idea

A CDN with custom domains lets your website use its own name while delivering content fast from servers near your visitors.

Think of it like...

It's like having a chain of local stores that sell your brand's products, so customers get what they want quickly, but the store signs still show your brand name.

┌───────────────┐       ┌───────────────┐       ┌───────────────┐
│   User A      │──────▶│ CDN Edge Node │──────▶│ Origin Server │
│ (New York)    │       │ (New York)    │       │ (Main Server) │
└───────────────┘       └───────────────┘       └───────────────┘
       │
       ▼
┌───────────────┐
│ Custom Domain │
│ www.example.com│
└───────────────┘

Build-Up - 7 Steps

1

Foundation

What is a CDN and why use it

Concept: Introduce the basic idea of a CDN and its purpose.

A CDN is a network of servers placed in many locations worldwide. It stores copies of website files like images and videos. When someone visits a website, the CDN sends files from the closest server to them. This makes the website load faster and reduces the load on the main server.

Result

Users experience faster website loading and less delay.

Understanding the CDN's role in speeding up content delivery is key to grasping why it improves user experience.

2

Foundation

Understanding custom domains and DNS basics

Concept: Explain what custom domains are and how DNS connects names to servers.

A custom domain is the website address people type, like www.example.com. DNS is like the internet's phone book that translates this name into the server's address. Without DNS, users would have to remember numbers instead of names.

Result

Learners know how domain names point to servers.

Knowing DNS basics is essential to understand how custom domains work with CDNs.

3

Intermediate

How CDNs use default domains

Concept: Show that CDNs provide a default domain but it may not match the website's brand.

When you create a CDN, it gives you a default web address like mycdn.azureedge.net. This works but looks different from your website's name. Visitors might see this unfamiliar address, which can reduce trust and brand consistency.

Result

Learners see why default CDN domains are not ideal for public websites.

Recognizing the limitation of default CDN domains motivates the use of custom domains.

4

Intermediate

Configuring custom domains with Azure CDN

🤔Before reading on: do you think adding a custom domain requires changing DNS records or just settings in Azure? Commit to your answer.

Concept: Explain the steps to link a custom domain to Azure CDN, including DNS changes.

To use your own domain with Azure CDN, you must add a CNAME record in your DNS that points your domain (like www.example.com) to the CDN's default domain (like mycdn.azureedge.net). Then, in Azure, you configure the CDN endpoint to accept your custom domain. This setup tells browsers to use your domain but get content from the CDN.

Result

Your website loads via the CDN but shows your own domain name.

Understanding the DNS role in linking custom domains to CDN endpoints is crucial for proper configuration.

5

Intermediate

Enabling HTTPS for custom domains

🤔Before reading on: do you think HTTPS works automatically with custom domains on Azure CDN or requires extra steps? Commit to your answer.

Concept: Describe how to secure custom domains with HTTPS on Azure CDN.

HTTPS encrypts data between users and the website, making it secure. Azure CDN can provide free SSL certificates for your custom domain, but you must enable HTTPS in the CDN settings. This process may take some time to issue and validate the certificate.

Result

Visitors see a secure lock icon and data is protected.

Knowing HTTPS setup is essential for security and user trust when using custom domains.

6

Advanced

Handling domain validation and certificate challenges

🤔Before reading on: do you think domain validation for HTTPS requires manual proof or is automatic? Commit to your answer.

Concept: Explain the domain ownership validation process for HTTPS certificates.

To issue an SSL certificate for your custom domain, Azure CDN must verify you own the domain. This usually involves checking the CNAME DNS record or adding a special TXT record. This step prevents others from using your domain without permission.

Result

SSL certificates are issued only after successful domain validation.

Understanding domain validation prevents confusion when HTTPS setup seems delayed or fails.

7

Expert

Optimizing CDN custom domain performance and security

🤔Before reading on: do you think custom domain setup alone guarantees best CDN performance and security? Commit to your answer.

Concept: Discuss advanced settings like caching rules, geo-filtering, and WAF integration with custom domains.

Beyond basic setup, you can configure caching rules to control how long content stays on CDN servers, improving speed and freshness. Geo-filtering can restrict content delivery to certain regions. Integrating a Web Application Firewall (WAF) protects your site from attacks. These settings work with your custom domain to deliver fast and safe content.

Result

Your website is faster, safer, and tailored to your audience.

Knowing these advanced options helps you fully leverage CDN capabilities beyond just custom domain setup.

Under the Hood

When a user requests content using your custom domain, the DNS directs the request to the CDN's edge server closest to the user. The CDN edge server checks if it has the content cached. If yes, it serves it immediately. If not, it fetches it from the origin server, caches it, and then serves it. The custom domain is linked via DNS CNAME records, so the user's browser sees your domain but receives content from the CDN transparently.

Why designed this way?

This design separates content delivery from domain naming to allow flexibility and scalability. Using DNS CNAME records avoids complex routing changes and leverages existing internet infrastructure. It also allows CDNs to serve many customers efficiently while letting each keep their brand identity.

User Request
   │
   ▼
┌───────────────┐
│ Custom Domain │
│ www.example.com│
└───────────────┘
   │ DNS CNAME
   ▼
┌───────────────┐
│ CDN Edge Node │
│ (Cache Check) │
└───────────────┘
   │ Cache Miss?
   ▼
┌───────────────┐
│ Origin Server │
│ (Main Content)│
└───────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does adding a custom domain to Azure CDN automatically enable HTTPS? Commit yes or no.

Common Belief: Adding a custom domain to Azure CDN automatically enables HTTPS with no extra steps.

Reality: HTTPS must be explicitly enabled and configured for custom domains; it is not automatic.

Why it matters: Assuming HTTPS is automatic can leave your site insecure, risking data interception and loss of user trust.

Quick: Do you think the CDN changes your website's IP address when using a custom domain? Commit yes or no.

Common Belief: Using a custom domain with CDN changes the website's IP address to the CDN's IP.

Reality: The IP address users connect to is that of the CDN edge server, but your origin server's IP remains unchanged and hidden.

Why it matters: Misunderstanding this can cause confusion in firewall rules or DNS setups, leading to access problems.

Quick: Is it true that once you set a custom domain on CDN, DNS changes are optional? Commit yes or no.

Common Belief: After configuring a custom domain in Azure CDN, you don't need to update DNS records.

Reality: DNS CNAME records must be updated to point your domain to the CDN endpoint; otherwise, traffic won't route correctly.

Why it matters: Skipping DNS updates means users won't reach the CDN, causing site downtime or slow loading.

Quick: Do you think caching rules on CDN always serve the freshest content? Commit yes or no.

Common Belief: CDN caching always serves the latest version of content automatically.

Reality: CDNs cache content based on rules and time-to-live settings; stale content can be served if not properly configured.

Why it matters: Ignoring caching behavior can cause users to see outdated content, harming user experience and business.

Expert Zone

1

Custom domain HTTPS certificates on Azure CDN can take hours to issue due to domain validation and propagation delays, which is often underestimated.

2

Using CNAME flattening or alias records is necessary for root domains (like example.com) because DNS standards don't allow CNAMEs at the root level.

3

Azure CDN supports multiple CDN profiles and endpoints, allowing complex setups where different custom domains point to different content origins or caching rules.

When NOT to use

Using a CDN with custom domains may not be ideal for highly dynamic content that changes every second, such as live data feeds, where caching delays cause outdated information. In such cases, direct server delivery or specialized streaming services are better.

Production Patterns

In production, companies use Azure CDN with custom domains combined with HTTPS and WAF for secure, branded, and fast delivery. They automate DNS and certificate management using Infrastructure as Code tools. They also monitor CDN logs and performance metrics to optimize caching and regional delivery.

Connections

DNS and Domain Name System

Builds-on

Understanding DNS is essential to configure custom domains correctly for CDN, as DNS controls how domain names point to CDN servers.

SSL/TLS Certificates and HTTPS

Builds-on

Knowing how SSL certificates work helps grasp why HTTPS setup for custom domains requires domain validation and certificate issuance.

Supply Chain Management

Analogy in logistics

Just like supply chains distribute products to local stores to reach customers faster, CDNs distribute content to edge servers near users, improving delivery speed and reliability.

Common Pitfalls

#1 Not updating DNS records after adding a custom domain to Azure CDN.

Wrong approach:

Configuring the custom domain in Azure CDN portal but leaving DNS CNAME record unchanged.

Correct approach:

Add a CNAME record in DNS pointing your custom domain to the Azure CDN endpoint domain.

Root cause:

Misunderstanding that DNS changes are required for traffic routing to the CDN.

#2 Assuming HTTPS is enabled automatically for custom domains.

Wrong approach:

Using custom domain on CDN without enabling HTTPS or waiting for certificate issuance.

Correct approach:

Enable HTTPS in Azure CDN settings and wait for the SSL certificate to be issued and validated.

Root cause:

Lack of awareness about the separate HTTPS setup process.

#3 Using a CNAME record at the root domain without alias or flattening support.

Wrong approach:

Creating a CNAME record for example.com pointing to CDN endpoint, which DNS does not allow.

Correct approach:

Use an alias or ANAME record if supported, or configure www subdomain with CNAME and redirect root domain to www.

Root cause:

Not knowing DNS standards prohibit CNAME at the root domain.

Key Takeaways

A CDN with custom domains lets your website keep its brand name while delivering content faster from servers near users.

Setting up a custom domain with Azure CDN requires updating DNS records and configuring the CDN endpoint to accept your domain.

HTTPS for custom domains is not automatic; you must enable it and complete domain validation to secure your site.

Understanding DNS, SSL certificates, and CDN caching behavior is essential to avoid common mistakes and ensure smooth operation.

Advanced CDN features like caching rules and security integrations help optimize performance and protect your website in production.