Skip to content

🌍 Configure DNS Domain

This Page Explains How EdgeHit function as a DNS Authoritative Server, and how to configure a User DNS Domain and System DNS Domain Under EdgeHit-CDN.

Difference Between User Domain and System Domain

In EdgeHit, DNS Domain created by User Account are User Domain, while DNS Domain created by Admin Account are treated as System Domain. The table below shows comparism:

Feature User Domain System Domain
Created by User / Admin System (automated or internal ops)
Stores - A records for CDN domains
- CNAME records		 - Site map
- Traffic policy
- A records for system nodes (e.g., EdgeHit nodes)
Purpose Used for external DNS resolution of user-owned or CDN-facing domains Used internally for routing, system control, and geo-based decision logic

πŸ›‘ Prerequisite

Before Using DNS Feature, user must have

  • A domain name that is managed under EdgeHit DNS or any other Domain Provider like Dynadot or GoDaddy, with NS record pointing to the coresponding DNS Group on EdgeHit

    Note

    Ensure that the NS record in DNS Group Iniatial Zone Record is the same as NS record configured on upstream DNS Server.

    • This can be done by configuring NS record on DNS Provider

  • Has an active EdgeHit Accout given to the user by Administrator, with DNS role enabled.

  • Has an active DNS Plan that is assigned to the user's account


Meanwhile, the system admin must have

  • Setup DNS Server Group
  • Added at least one DNS Server to the Server Group
  • Defined all the prerequisite setting for all of above such as IP Address list, CDN Server Group, DNS Server Group & Initial Record, etc

For more, please refer to Adding DNS Server


🧬 Add System DNS Domain

System DNS Domain is a DNS Domain Zone Created by admin. It serve different purpose than User DNS Domain.

Instead of Storing DNS Record for User Origin Server, It stores System DNS Record such as Site Map and Traffic Policy. In some setup, it also contain DNS Record for the hostname of EdgeHit Controller Load-Proxy or any component in the infrastructure.

Below Show example of a System DNS Domain:

alt text

Note

System DNS Domain does not have a coresponding User and User Plan.

below shows an example of DNS record in system domain

alt text

Note

you do not need to manual define or edit Traffic Policy or Site Point. They are manually created and updated once Traffic Policy and CDN Domain is configured

  1. Navigate to DNS > Domain section on the side bar. , select add button to define a new Domain Zone

    Tip

    The following Step are for setting up a System Domain which closely resembled setting up a user domain. The only difference is this configuration is done under admin account and the System Domain does not belong to any User.

    Pic

  2. Define the Domain Origin (zone apex ) in the settings. Note that this setting COULD NOT be changed and will mapped to @ variable to serve FQDN records. Define the DNS Server Group that will serve this Domain Zone. The DNS Server Group will bootstrap the SOA and NS record in the Zone.

    Pic

    Note

    When adding a domain zone under the admin account, you are defining a system DNS domain zone, which is different in content of user DNS domain. System DNS domain can create mapping from user DNS domain to EdgeHit nodes IP to route traffic into the CDN Network.


  3. Once the Domain is Created, it will apear under the table in DNS > Domain section. Click on Details to edit the Domain Zone.

    Pic

  4. Go to the Records tab. Click on Add button to add DNS Record.

    Pic

  5. Select the type of record you want to add. Then Define the coresponding Name and Content. You can add multiple record by clicking again on the add button, edit Record by Details action or Delete the Record.

    Pic

    Note

    If you want to edit the NS record or SOA record of a Domain, it is advisied to edit from the respective DNS Group's INITIAL RECORDS

Pic

Tip

ensure that initial NS record is also present on Upstream DNS Server by adding the record in DNS Provider such as Dynadot, GoDaddy, etc.


πŸ‘₯ Add User DNS Domain

🎁 Configure DNS User Plan

This section show how to configure DNS User Plan , which is needed before defining a DNS Domain in user account.

System Admin needs to define DNS User Plan for user in DNS > User Plan > Add Section.

Info

DNS User Plan is needed as User Account ( Non-Admin) can only create DNS Domain by applying DNS Plan assigned to the User as a configuration template.

  • They cannot define DNS group manually like in admin account. This setup restrict use case and prevent violation.

alt text

DNS User Plan defines the DNS Server Group as a configuration template of DNS Domain. It also limits how many DNSRecords User can define. Details will be explained in Advanced User Plan Configuration

  • DNS erver Group define a group Of EdgeHit DNS Server that are responsible to store the DNS Domain Record as a DNS Zone File.


🌍 Configure User DNS Domain

  1. As User account, Navigate to DNS > Domain section on the side bar. , select Add button to define a new Domain Zone Pic

  2. Define the Domain Origin (zone apex ) in the settings. Note that this setting COULD NOT be changed and will mapped to @ variable to serve FQDN records.

    • Define the DNS Server Group that will serve this Domain Zone. The DNS Server Group will bootstrap the SOA and NS record in the Zone.

    Pic

    Tip

    User Account has no permission to create a DNS server group. such setting must be done by admin via adding EdgeHit DNS as DNS Server & Configuring DNS Group. Refer to Add EdgeHit DNS as DNS Server


  3. Once the Domain is Created, it will apear under the table in DNS > Domain section. Click on Details to edit the Domain Zone.

    Pic

  4. Go to the Records tab. Click on ADD button to add DNS Record.

    Pic

  5. Select the type of record you want to add. Then Define the coresponding Name and Content. You can add multiple record by clicking again on the add button, edit Record by Details action or Delete the Record.

    Pic

    Note

    If you want to edit the NS record or SOA record of a Domain, it is advisied to edit from the respective DNS Group's INITIAL RECORDS


🩺 Configure DNS HealthCheck

Prerequisite

In order for DNS HealthCheck to work, ensure that all EdgeHit DNS Instance in the Server Group assigned to the DNS Domain that contain Healthcheck ID section have EdgeHit DNS_health_check_url value configured in thier .env file

  1. Login into LoadUP-CP Dashboard and go to the Check > Task Section . Click on Add Task

    Pic

  2. Define a new task to monitor target IP. Select the LoadUP-worker node that is responsible to execute the monitoring task.

    Choose the type to be ICMP or HTTP and define other stated config sucg as timeout and interval, Click on Save Changes once you are done.

    Note

    USE IP ADDRESS as Target instead of Domain Name. You can define the Domain Name for Target IP in the Name Section of the Task as Reference.

    Pic

  3. Once You click on Save Changes, you will be prompted with the task details. Note Down the Task UUID. You can also view the details of monitoring status in the Records section

    alt text

    alt text

  4. Login into EdgeHit Controller Dashboard and go to the DNS > Domain > Details > Records Section of the Coresponding Domain. Click on Add to define new DNS Record

  5. Define The DNS Record content that equal to IP address of previously declared HealthCheck Task. Then, fill in Task UUID as Health Check ID of the DNS Record. Pic
    Pic

  6. Once Configured, you Record tab would look similiar as below with HealthCheck ID column
    Pic

  7. You can verify the status of the DNS Request by issue a DIG command on local terminal to the DNS Record. You can also manually prompt http://<HealthCheck Domain>:16666/health-dns.txt to verify the status of the Target IP Pic