Setting up a DNS Zone

Overview

You can use this document to set up a DNS zone for an existing domain. To complete this process, you must also add records to the newly created done. Afterwards, you will be able to configure your DNS zone.

Before you begin:

To view supported DNS record types, see View Supported DNS Record Types.

Step 1: Create a zone

1. In the StackPath Control Portal, in the left-side menu, click Stacks.
2. Select a stack.
   • The portal will refresh with additional sections.
3. In the left-side menu, select DNS.
4. Click Create DNS Zone. 
5. Enter your website's domain name.
   • Do not include subdomains (www, CDN) or protocols (HTTPS).
6. Click Continue. 
7. StackPath will scan your domain to locate existing records. 
   • If no records are located, then click Continue. You will add records in a later step. 
   • If records are located, review the list of records.

Step 2: Add DNS records 

You can use these instructions to manually add DNS records. 

• As an option, if you have access to your entire Zone File from your current provider, then you can import your records via Zone file. To learn more, see How-To Import A DNS Zone File.

1. In the DNS Records screen, click Add Record. 
2. Update the blank fields. 
   • Review specific instructions for apex domains and subdomains:
     

     Apex domains	Subdomains	All domain types
     For apex domains (root domains), in Name, you must enter an ampersand ( @ ). This action will cause the apex domain to resolve to the IP address that you will enter in Value.	For subdomains, in Name, you must only enter a subdomain, such as www. Additionally, to create a wildcard subdomain record, in Name, enter an asterisk ( * ).	StackPath recommends that you initially enter a short time period to avoid possible troubleshooting issues with propagation.

      
   • Review specific instructions for supported record types: 

     Type	Name	Value	TTL
     A	Enter a valid apex or subdomain entry.	Enter a valid IPv4.	Enter a length of time before the DNS cache expires for the record, and a new request must be made.
     AAAA	Enter a valid apex or subdomain entry.	Enter a valid IPv6 address.	Enter a length of time before the DNS cache expires for the record, and a new request must be made.
     CNAME	Enter a valid subdomain entry. For subdomains, any text you enter in Name will be placed in front of your apex domain. As a result, if you put your entire domain in Name, then DNS record will malfunction. For example, if you type www.examplesite.com in Name, then the record will attempt to work via www.examplesite.com.examplesite.com.	Enter a valid Fully Qualified Domain Name (FQDN).	Enter a length of time before the DNS cache expires for the record.
     MX	Enter a valid apex or subdomain entry.	For Server, enter a valid IMAP (incoming) or SMTP (outgoing) server address. For Priority, select a number where 1 is the most important, and 10 is the least important.	Enter a length of time before the DNS cache expires for the record.
     TXT	Enter a valid apex or subdomain entry.	Enter a valid string.	Enter a length of time before the DNS cache expires for the record.
     NS	Enter a valid valid subdomain entry.	Enter a valid NS address. (Domains with NS records will need to be managed with the DNS provider that the NS record resolves to, which is the authoritative nameserver.	Enter a length of time before the DNS cache expires for the record.

3. Click Save. 

Step 3: Verify DNS status

As an optional step, StackPath recommends that you verify your DNS status. 

It may take 24 hours (or in some cases 48 hours) for your records to globally propagate. 

It is important for your DNS to be completely propagated before you make changes to a live website or a CDN. If you prematurely update your website, your users may have issues accessing your website.

1. Use a third-party tool, such as What's my DNS?.
2. Update the search parameters to reflect the Type and Name you entered in the portal, and then perform a search. 
3. Verify that the listed results match the Value you entered in the portal. 

Step 4: Add StackPath name servers 

After you have duplicated your existing DNS servers onto the portal, you must point your domain registrar to the StackPath name servers. This action will cause your traffic to be directed to the StackPath DNS servers.

In this step, you will need to access your hosting registrar's portal.

1. In the left-side navigation, click DNS.
2. Under Action, click the vertical ellipses for the desired DNS zone, and then select Edit. 
3. Locate and copy the name servers. 
4. Access your hosting registrar's portal, and then paste the copied name servers to your registrar. 
   • If you need help updating your registrar, see How-To Configure DNS for CDN/WAF with Your Provider and locate your specific DNS provider. 
   • Changes may take up to 24 hours to take effect. 
5. After you have updated your registrar, StackPath recommends that check your DNS status. 
   1. Access a third-party tool (like What's my DNS? ), and then enter your domain into the search field. 
   2. Update the record type to NS, and then perform a search. 
   3. Verify that the listed locations display the name severs you updated in your registrar. This information will indicate that any change you make in the portal will reflect on your live site. 

Related documentation

To troubleshoot common DNS issues, such as name server propagation problems, see Debugging common DNS issues.