🌐Configure DNS Zone
Last updated
Last updated
Once your project is created, you need to set up a new DNS zone for it so that requests to your application’s domain can be properly resolved by the Edgeport platform.
To do this, follow the guide below.
Note: While we recommend using Edgeport DNS, it's not mandatory to access the platform's services, such as ADN, WAF, and others.
You can point your domain to our services from any DNS provider, bypassing the steps outlined in the following instructions. However, this could lead to variances in performance and security, which may differ from the enhanced productive capacity and vulnerability protection that our integrated DNS solution offers.
Choose the required project within the Edgeport dashboard by clicking on its URL.
Once inside, navigate to the Routing section in the left-hand menu.
Read the introductory message and click the Create First Record button below.
In the opened frame, enter your application’s domain address (edgeport.info in our case).
This will define the specific DNS namespace that Edgeport's name servers will have authority over when handling DNS queries.
Do not include subdomains (like www., cdn., etc) and protocols (like http://) here.
Confirm this action by selecting Create.
In the opened screen, you’ll be provided with the information on the platform’s name servers (we will return to this later in this instruction) and options for managing the DNS records within the newly created DNS zone.
To start with, pay attention to the expandable Default records section at the bottom of the frame:
By clicking on it, you will access the complete list of DNS records that are automatically configured when a new DNS zone is created:
Pat attention that these default records cannot be edited or deleted. All the records you add manually will also be listed below the default entries in this roster.
To make navigation easier, use the Type selection on the right to filter the list by record type. Additionally, you can locate a particular string by specifying the appropriate Name, Type, or Value within the search field above.
When you're ready to add a new record, click the same-named button to the right:
For this tutorial, we’ll add an A-Record to point the IPv4 address to our example project’s domain.
In the appeared frame, you need to specify the following properties:
Type of the added record - choose one from the drop-down list (A (IPv4 Address) in our case)
Name - the preferred record label (can contain alphanumeric characters, the ampersand (@) symbol, underscores, hyphens, and periods; herewith, for address records, there are specific rules governing the value of this field)
TTL - the number of seconds a server should keep the record cached during the requested interval.
Value of the record (the particular content depends on a record type - you’ll see a shadowed hint within this field, designating a specific format needed; IPv4 address in our case)
Finish by clicking Add.
Note that the new address record will not be created until the whole zone configuration is saved - for now, it’s just added to the list.
For more information on managing DNS records and their supported types, please consult the linked guides.
After all the records are set up, let’s return to the central My Name Servers section, which displays the list of the platform’s name server domains.
At this step, you should log in to your domain registrar account and replace the current name servers with Edgeport’s ones (ns1.edgeport.net, ns2.edgeport.net, and so on) in the DNS configuration. The exact flow may vary depending on your specific registrar company.
You can also notice the Vanity name servers toggle switch within this frame section - by enabling it, you’ll reveal the list of corresponding IP addresses that point to name server domains.
Use these addresses while configuring the DNS settings within your registrar in order to mask the public DNS service and designate the branded-named servers like ns1.yourcompany.com instead.
This allows you to keep uniformity throughout DNS records, extend your branding to the technology stack, and customize the WHOIS information for your domain.
Once everything’s set up, click the “I confirm that I configured the name servers” button above.
Please pay attention that while DNS changes are deployed instantly, it can take up to 24 hours for your records to propagate globally.
It is essential for your DNS to propagate completely before making changes to a live website or a CDN; otherwise, your users may experience issues accessing your website.
You can use third-party tools like What's my DNS? to perform a quick DNS lookup of your domain name's current IP address, pointed name server(s), and other record information across multiple DNS servers worldwide.
As the next configuration step, we suggest issuing a dedicated SSL certificate to enable the establishment of a secure HTTPS connection to your application.
