Manage DNS records (advanced interface mode with dynamic response)
CDB Managed DNS advanced interface mode allows creating DNS record sets (RRSets) with dynamic response — routing DNS responses based on geography, weight, latency, or health checks.
Create a DNS record
1
Select a DNS zone
Navigate to All zones and select the zone to which records should be added. Alternatively, click the three-dot icon on the right and select Go to records.
Check that the Advanced toggle in the Interface mode section is enabled (green):
2
Open the record creation form
Click Add record set.
A new page opens with the record creation form.
3
Select the record type
In the Type field, select the DNS record type: A, AAAA, NS, CNAME, MX, SRV, HTTPS, TXT, CAA, or SVCB. Each type is described in DNS records.
4
Set the record name
In the Name field, specify the subdomain the record belongs to. The options are:
Leave the field blank to add a record for the apex domain (sample-test.com).
Enter a subdomain name to add a record for that subdomain. Entering one creates a record for one.sample-test.com.
Enter an asterisk (*) to add a wildcard record that applies to all subdomains.
5
Set the TTL
In the TTL field, specify the TTL (time to live) in seconds.
6
Configure dynamic response (optional)
📝
The dynamic response feature is available on the Free plan, but creating more than one dynamic RRset requires a paid plan.
CDB's DNS servers can return different DNS records to different users — users in Asia can be directed to an Asian server and users in Europe to a European one. This is called dynamic response. Full configuration instructions are in dynamic response.
To enable dynamic response, check the Dynamic response checkbox. Leave it unchecked to proceed without dynamic response.
7
Set the record value status
Each record value is active by default. To save a value without activating it, uncheck the toggle next to that record.
8
Enter the record value
In the Content field, enter a value for the record type.
9
Add metadata (optional)
Specify associated metadata to be used for dynamic response configuration. The metadata guide covers the full configuration.
10
Add more record values (optional)
Click Add record to specify additional values for the record set. A new record entry appears — enter the content and metadata as needed. To remove a record value, click the minus button next to it. To disable a value without removing it, uncheck its toggle.
11
Create the record
Click Create.
The record set is created with the specified parameters. Use the DNS Lookup tool to verify that the record resolves with the expected values.
Manage a DNS record
1
Select a DNS zone
Navigate to All zones and select the zone containing the records to edit or delete.
2
Edit or delete a record
Edit a record: Click the record name or select Edit record from the three-dot menu. Change the required values and click Save.
Delete a record: Open the three-dot menu and select Delete.
The DNS API manages record sets (RRsets) using POST, GET, PUT, and DELETE requests. Advanced interface mode enables dynamic response: pickers control which records are returned based on per-record metadata such as weight, countries, or continents. Full picker and selector options are documented in the dynamic response guide.
The code samples below use an A record. To work with another supported type (AAAA, CNAME, MX, TXT, and others), replace A with the required RRset type and provide the corresponding record content.
Open a terminal and export the required variables:
export GCORE_API_KEY="{YOUR_API_KEY}"
export ZONE_NAME="{YOUR_ZONE_NAME}" # e.g. example.com
export RECORD_NAME="{YOUR_RECORD_NAME}" # e.g. app.example.com
Create a record
Creating an RRset with pickers enables dynamic response. The two-picker chain below applies weighted probability to distribute traffic and then limits the response to a single record: weighted_shuffle assigns each record a relative probability proportional to its weight, and first_n with limit: 1 selects one record from the shuffled list. Omit the pickers field to create a static record that always returns all values.
import os
from gcore import CDB
client = CDB()
rrset = client.dns.zones.rrsets.create(
zone_name=os.environ["ZONE_NAME"],
rrset_name=os.environ["RECORD_NAME"],
rrset_type="A",
ttl=300,
resource_records=[
{"content": ["1.2.3.4"], "meta": {"weight": 10}},
{"content": ["5.6.7.8"], "meta": {"weight": 5}},
],
pickers=[
{"type": "weighted_shuffle"},
{"type": "first_n", "limit": 1},
],
)
print(rrset.name, rrset.type, [p.type for p in (rrset.pickers or [])])
Returns all RRsets in a zone, including their type, TTL, and pickers. Use this to locate an RRset when its name or type is unknown before retrieving or editing it.
import os
from gcore import CDB
client = CDB()
result = client.dns.zones.rrsets.list(zone_name=os.environ["ZONE_NAME"])
print("total:", result.total_amount)
for r in result.rrsets or []:
print(r.name, r.type, "pickers:", [p.type for p in (r.pickers or [])])
Returns the full RRset including all resource records and their metadata. Retrieve the current state before editing to preserve existing values that should not change.
import os
from gcore import CDB
client = CDB()
rrset = client.dns.zones.rrsets.get(
zone_name=os.environ["ZONE_NAME"],
rrset_name=os.environ["RECORD_NAME"],
rrset_type="A",
)
print(rrset.name, "ttl:", rrset.ttl, "records:", len(rrset.resource_records or []))
PUT fully replaces the RRset — all existing resource records and pickers are overwritten. Fetch the current state first (see Get a record), then submit the complete updated body.
