• Product Introduction
  • Quick Start
    • Importing a Git Repository
    • Starting From a Template
    • Direct Upload
    • Start with AI
  • Framework Guide
    • Frontends
    • Backends
    • Full-stack
      • Next.js
      • Nuxt
      • Astro
      • React Router
      • SvelteKit
    • Custom 404 Page
  • Project Guide
    • Project Management
    • edgeone.json
    • Configuring Cache
    • Error Codes
  • Build Guide
  • Deployment Guide
    • Overview
    • Create Deploys
    • Manage Deploys
    • Deploy Button
    • Using Github Actions
    • Using CNB Plugin
    • Using IDE PlugIn
    • Using CodeBuddy IDE
  • Domain Management
    • Overview
    • Custom Domain
    • HTTPS Configuration
      • Overview
      • Apply for Free Certificate
      • Using Managed SSL Certificate
    • Configure DNS CNAME Record
  • Observability
    • Overview
    • Metric Analysis
    • Log Analysis
  • Pages Functions
    • Overview
    • Edge Functions
    • Cloud Functions
      • Overview
      • Node Functions
  • KV Storage
  • Edge AI
  • API Token
  • EdgeOne CLI
  • Pages MCP
  • Integration Guide
    • AI
      • Dialogue Large Models Integration
      • Large Models for Images Integration
    • Database
      • Supabase Integration
      • Pages KV Integration
    • Ecommerce
      • Shopify Integration
      • WooCommerce Integration
    • Payment
      • Stripe Integration
      • Integrating Paddle
    • CMS
      • WordPress Integration
      • Contentful Integration
      • Sanity Integration
    • Authentication
      • Supabase Integration
      • Clerk Integration
  • Best Practices
    • Using General Large Model to Quickly Build AI Application
    • Use the DeepSeek model to quickly build a conversational AI site
    • Building an Ecommerce Platform with Shopify
    • Building a SaaS Site Using Supabase and Stripe
    • Building a Company Brand Site Quickly
    • How to Quickly Build a Blog Site
  • Migration Guides
    • Migrating from Vercel to EdgeOne Pages
    • Migrating from Cloudflare Pages to EdgeOne Pages
    • Migrating from Netlify to EdgeOne Pages
  • Troubleshooting
  • FAQs
  • Contact Us
  • Release Notes

Configure DNS CNAME Record

A CNAME record is used to point a domain name to another domain name, commonly used for CDN acceleration or corporate email settings. After you add a custom domain to the Pages Project, you need to configure the appropriate CNAME record at the domain name registrar to access the Pages Project via the domain name.

This document takes GoDaddy as an example and combines the official documentation to organize the following detailed process.


Log in to the GoDaddy Console

Access GoDaddy Console and ensure that you are logged in.
This step ensures that the domain name is hosted on GoDaddy. If it is unhosted, you can purchase a domain name via console first.


Entering Record Management Page

In the "Domain" list, find the target Domain name, click to enter the details page and switch to the DNS Tab.



Adding a CNAME Record

Click the "Add New Record" button on the page to pop up the new record settings form.




Fill in the Following Fields

Type: Select "CNAME" in the pull-down menu.
Name: Enter a subdomain (for example, "www" indicates www.example.com) or enter "@" to represent the primary domain name. Note that if the host record is "@", it may affect the normal resolution of the MX record. Operate with caution.
Value: Enter the CNAME record value provided by Pages, for example, "a4285573.xxx.example.com.dns.edgeone.site.". Note that only the domain name can be filled in, and the IP address cannot be included.
TTL: Cache time, default 1/2 Hour (30 minutes). If you need faster global effect, you can reduce this value, but it is not recommended to set it too low.

After completing, click "Save" to save.


Verification and Coming Into Effect

After the settings are completed, you can use the DNS query tool for verification. For example, input nslookup -qt=cname www.example.com (Windows) or dig www.example.com (Mac/Linux) in command line to confirm that the CNAME record points to correctly.

The time it takes for a CNAME record to take effect depends on the TTL setting, usually from several minutes to several hours. If it is not effective, you can wait and re-verify.

After completing CNAME configuration, the platform will automatically detect whether the current CNAME status is effective. If the domain management list displays the current CNAME as effective in the status column, the current domain name has been correctly configured and acceleration is activated.


If you have correctly configured the CNAME but the current status still shows as inactive, it might be due to the DNS service provider's CNAME resolution effective delay. You can also manually verify in the following ways.
Mac/Linux
Windows
On Mac/Linux systems, you can use the dig command to verify. For example, for the domain name www.example.com, you can run the command in the terminal: dig www.example.com. Based on the parsing result, you can check the CNAME information of the domain name. If the CNAME information is identical to the CNAME address assigned by EdgeOne, it means domain name acceleration has been switched to EdgeOne.

On Windows system, open cmd to run program. For example, for the domain name www.example.com, you can run in cmd: nslookup -qt=cname www.example.com. Based on the parsing result, you can view the CNAME information of the domain name. If the CNAME result is the CNAME address assigned in EdgeOne, it means acceleration has been switched to EdgeOne.


ai-agent
你可以这样问我
如何开始使用 EdgeOne Pages?