# CNAMEs
The **Settings > CNAMEs** service menu section provides you with the capability to associate the custom domain name(s) of your project with your service’s ADN and CDN addresses at the Edgeport platform. This empowers you to establish a branded and unified online presence for your service while enhancing accessibility and user experience.
Upon navigating to this section, you'll find the default CNAME records for both ADN and CDN platforms already present in their respective panes. These records were automatically generated upon the [addition of your service](https://docs.edgeport.com/product-docs/start-guide/add-a-new-service) to the platform.
Below, we'll explore both of the presented panes and the options they provide:
* [ADN CNAMEs](#h.h6r3b1hnswxi)
* [CDN CNAMEs](#h.tiei9999v2lo)
### ADN CNAMEs
The Application Delivery Network (ADN) within the Edgeport platform serves as the central component responsible for delivering the main application domain. It encompasses a wide array of functions, including content delivery, load balancing, security, and web application optimization.
Also, it plays a pivotal role in accelerating the processing of dynamic requests (such as login credentials, account-specific information, user preferences, etc) and provides the ability to cache them on the edge. Herewith, the entire website can be efficiently delivered through the ADN platform, eliminating the need for CDN involvement if you prefer such an approach.
As a best practice, ADN is responsible for delivering custom domain names associated with a whole site, such as:
* *example.com*
* *[www.example.com](http://www.example.com)*
* *docs.example.com*
* *blog.example.com*
Your project is already equipped with a default CNAME configuration that directs your application domain name, provided during its addition to the Edgeport platform, to the dedicated ADN-related internal address within the platform's network. \
\
This domain name is labeled as *Primary* as the very first added one.
To add a new custom domain name record, click the **Add New CNAME** above the pane:
In the popped-up window, input the desired custom domain name and choose **Add**:
The specified CNAMe will instantly appear on the list.
For the newly added line, you will see a set of options available:
* **Set Redirect to Primary Domain** - allows you to route traffic from this new domain to the one labeled as Primary. More information on this option can be found in the [Set Domain Redirect](https://docs.edgeport.com/product-docs/how-to/set-up-domain-redirect) guide;
* **Set Primary** - helps to switch the main domain name associated with your service to the chosen one;
* the **pencil** **icon** - allows you to edit the previously added CNAME address;
* the **bin****icon** - is intended for removing a specific CNAME record from the list.
{% hint style="info" %}
Please **Note**:
* Any changes made within this list may take **up to 60 minutes** to be fully propagated across all PoPs in the edge network.
* For the traffic to be directed to your application via a newly added CNAME, you need to add the corresponding CNAME-type record to your [DNS settings](https://docs.edgeport.com/product-docs/service-menu/routing). This record should contain the appropriate domain name stated as a ***Name***, and your project’s Edge address (displayed within the *POINTS TO* column in the screen above) stated as a ***Value***.
* If you already have an SSL certificate deployed for your service, you’ll need to [update it](https://docs.edgeport.com/product-docs/start-guide/issue-ssl-certificate/update-ssl-certificate) with the newly added domain(s) to ensure the seamless functioning of the HTTPS service.
{% endhint %}
### CDN CNAMEs
The Content Delivery Network (CDN) component within the Edgeport platform is responsible for accelerating the delivery of static assets, including images, CSS stylesheets, embedded videos, Javascript files, and more. Caching these elements on the edge not only boosts loading speed and performance for your project by means of parallelized downloads but also significantly reduces the load on your application's origin servers.
Utilizing both ADN and CDN for your service delivery enables you to segregate the processing of dynamic and static requests, which results in a more cost-efficient distribution and enhanced management efficiency.
Typically, CDN content delivery points are assigned to subdomains like:
* *cdn.example.com*
* *static.example.com*
* *assets.example.com*
Upon adding your service to the platform, you get the default CDN CNAME already configured within your service settings.
To add a custom (e.g., brand-reflecting) domain for your project’s CDN, click on the **Add New CNAME** button above the corresponding list.
Enter the desired domain name to be used as a CDN point and select **Add**:
The newly added CNAME record will instantly appear on the list.
You can manage the added records using the available icons; they allow you to **edit**or **remove**a record at any time (only the initial CDN CNAME is neither editable nor removable).
{% hint style="info" %}
A few **important points** to remember:
* After making changes in this list, allow **up to 60 minutes** for them to be fully propagated across all PoPs within the edge network.
* For the traffic to be directed to your application via a newly added CNAME, you need to add the corresponding CNAME-type record to your [DNS settings](https://docs.edgeport.com/product-docs/service-menu/routing). This record should contain the appropriate domain name stated as a ***Name***, and your project’s Edge address (displayed within the *POINTS TO* column in the screen above) stated as a ***Value***.
* If you already have an SSL certificate deployed for your service, you’ll need to [update it](https://docs.edgeport.com/product-docs/start-guide/issue-ssl-certificate/update-ssl-certificate) with the newly added domain(s) to ensure the seamless functioning of the HTTPS service.
{% endhint %}
