OpenResty Edge can be used as authoritative DNS servers.
As show in the following diagram:
Without considering DNS caching, the client resolves
example.com in two stages.
- querying the root DNS server for the authoritative server address of
- querying the authoritative server of
example.comfor the address of
If you wish to use the OpenResty Edge gateway nodes as the authoritative servers, you need to resolve the authoritative server to the gateway node.
DNS is enabled before using the DNS service.
Create DNS applications
Select and click on the
DNS tab to create a new DNS application.
Enter the domain name to be resolved and the domain name server as instructed, e.g. example.com and ns1.example.com/ns2.example.com, respectively.
Resolve to gateway node
Go to admin console of your domain name providers. Resolve the name of domain name server (e.g. n1s.example.com above) to the gateway node.
For example, for the Godaddy users, you may go to Godaddy Admin Console and add two hostnames ns1 and ns2 first, with the IP address point the Edge gateway node IP. Then set ns1.example.com / ns2.example.com as the domain name servers.
Once the NS record take effect, the gateway node will be capable of DNS service.
Add DNS records
Choose the created DNS application in the DNS application list, and click it to add a DNS record.
The following types of DNS records are permitted: A, AAAA, CNAME, MX, TXT, and NS. Besides, the resolve can be pointed to different gateway nodes depending on the network types for users,
The currently optional network types are Country, Region and Operator.
Automatically select proper DNS records
When creating a DNS record, users may choose the network segment corresponding to that record, and Edge will return the matching DNS record via the requested IP address
or via cidr
Calculate recommended configuration
Calculating the recommended configuration is an alternative to manually configuring each DNS record
Type in the configuration and a proper DNS record will be generated fit for that configuration
DNS Record Priorities
OpenResty Edge can be configured with different DNS resolution records for different network sources. For example, the following two DNS records are configured.
- DNS request from California resolves to the IP
- DNS request from the USA to the IP
For such DNS records with inclusion relationships, OpenResty Edge resolves them on a precision first basis. For example
- if the client is from California, rule 1 will be applied and resolve to
- if the client is from a non-California region of the US, rule 2 will be applied and resolve to
Active-standby settings supported for DNS records
DNS records having totally the same type + record + network type can mutually act as active and standby records
The default setting is using the active DNS record only, but the backup DNS record will also be used in the following situations:
- There is no active DNS record
- After the health check is enabled, the active DNS record is found unhealthy
Enable DNS health check
Open DNS health check on the DNS application editing page
The following meanings apply to the configuration options:
- Port: edge admin will examine whether the IP + configured port of a DNS record posts normal communication. Only one port is allowed to be configured for each DNS application
- Timeout period: Examine the TCP connection timeout every time. If a normal connection cannot be established within the specified time, the examination result will be marked as a failure.
- “Unhealthy” threshold: The DNS record will be deemed unhealthy if the times of failure spotted in examination exceed this threshold.
Health check is temporarily applicable only to DNS records of A and AAAA types. Unhealthy DNS records will be compulsorily taken offline.
Not healthy state:
Bind DNS to k8s cluster
You can bind a DNS to a k8s cluster.
Edge will manage DNS record automatically.
Switch map to kubernetes on, select k8s cluster, click Create Button.