This article explains how to create DNS record sets (RRSets) in Gcore DNS Hosting advanced mode. Interface mode differences are described in our article about Gcore DNS.
To check if advanced mode is enabled, navigate to the DNS section of the Gcore Customer Portal. Ensure the toggle is enabled/green in order to continue managing DNS records according to this guide:
In the Gcore Customer Portal DNS area, open the All zones tab and select the domain zone for which you want to add records. Either click the domain zone (either via “Quick zone selection” list on the left or under "Zone" in the main table) or click on three dots opposite the domain zone and then choose Go to records.
The page with your existing DNS records will open. Click Add record set.
A new page will open. Perform steps 2-7 there. The numbering in the image below refers to the steps that follow.
In the “Type” section, select the type of DNS record you want to create: A, AAAA, NS, CNAME, MX, SRV, HTTPS, TXT, or CAA. Learn more about them in our article about supported DNS record types.
In the “Name” field, specify to which domain or subdomain the record belongs. You have three options:
one.sampledomain.com
, one
is a subdomain) to add a record for the particular subdomain.*
to add a record for all subdomains at once (wildcard record.)In the "TTL" field, enter the interval in seconds for which your domain records should be cached.
Let's take an example of an A record with a TTL of 300 seconds, equal to 5 minutes. Say you change the value of this record from 10.0.0.1
to 10.0.0.0
. For up to 5 minutes, users requesting your domain will get a server with IP 10.0.0.1
(this value will be stored in the cache of recursive DNS servers). However, within a maximum of 5 minutes, the DNS server will see the new value of the A record and refresh its cache. When your domain is requested, the DNS server will send users to the server with IP 10.0.0.0
.
The point within the 300-second interval at which you changed the record determines how long it will take for users to access the new record. If you change the record 240 seconds into the TTL, users will wait only one minute; if you change it at 1 second, they will wait 4 minutes and 59 seconds. So, choose a TTL duration according to your maximum wait-time tolerance.
The dynamic response feature is also available for the Free plan, but to create more than one dynamic RRset you'll need a paid plan.
Gcore's DNS servers can give different DNS records to different users. For example, you can opt to send users in Asia to an Asian server and users in Europe to a European one. This is called dynamic response. Learn how to configure it in detail in our dedicated article.
To enable dynamic response, enable the "Dynamic response" toggle. If you don't require balancing, leave it disabled and go to step 6.
You can also configure the dynamic response feature via API requests using dynamic RRsets. For more information about pickers and selectors, read the API documentation.
Fill in the “Content” field with an appropriate value for your record type:
Record type | Value |
A | The IP address (IPv4) of the server of the web page that will open by your domain name. Example: ```128.128.128.128``` |
AAAA | The IP address (IPv6) of the server of the web page that will open by your domain name. Example: ```7625:0d18:1fa3:07d7:1f44:8a2e:07a0:678h``` |
NS | The name of the zone you want to delegate your domain to. Example: ```ns1.smth.com``` |
CNAME | The domain or domain zone name that your domain should refer to. Example: ```uuuuu8.cdn.co``` |
MX | The name of the mail server that receives mail for your domain. Example: ```ASPMX.L.GOOGLE.COM``` If you are using multiple mail servers, fill in the “Priority” field for each server. The lower the value in this field, the higher the priority. |
SRV | The canonical name of the machine providing the service. Example: ```_sip._tcp.example.com. 3600 IN SRV 10 50 5060 sipserver.example.com``` |
HTTPS | HTTPS is a resource record that provides information and parameters for how to access a web service available via HTTTS. Example: *example.com. 1800 IN HTTPS 1 . alpn=h3,h3-29,h2 ipv4hint=1.2.3.4,9.8.7.6 ipv6hint=2001:db8:3333:4444:5555:6666:7777:8888, 2001:db8:3333:4444:CCCC:DDDD:EEEE:FFFF* |
TXT | Text information the record should contain. Example: ```logmein-verification-code=976afe6f-8039-40e4-95a5-261b462``` |
CAA | Defines the certificate authorities who are allowed to issue an SSL/TLS-certificate for the domain name. The recording consists of three parts which are separated by a space. ```CAA [flags] [tag] "[value]"``` The "value" must be enclosed in double-quotes (""). Example: 0 issue "comodo.com" |
You can also specify associated metadata, which is used for dynamic response configuration. Learn more in our dedicated metadata guide.
To add multiple records of the same type, click Add record. A new line will appear. There, enter the content of the next record and associated metadata if needed. You can also delete any record by clicking the "—" button next to it or disable it via its toggle.
After completing the configuration, click the Create button. DNS records with the specified parameters will be created.
You can check if the created record has been added correctly using the Gcore DNS Lookup tool.
1. Open the record settings as described in step 1 of the instructions above.
2. Click on the three dots next to the desired resource record or on its name. In the menu that appears, click Edit.
3. Make the necessary changes.
4. Click Save or Save and Close to apply the new settings.
1. Open the record settings as described in step 1 of the instructions above.
2. Click on the three dots next to the desired resource record or on its name. In the menu that appears, click Delete.
3. Confirm the deletion when prompted.
Was this article helpful?
Learn more about our DNS hosting