DNS
Service Overview
Our DNS management platform allows you to configure and manage domain zones and resource records via an intuitive dashboard or API.
Key Features:
- Create & manage DNS zones for your domains
- Add, edit, or delete resource records (
A
,AAAA
,CNAME
,MX
,TXT
, etc.) - Delegate domains to our nameservers
- DNS requests stat with detailed analytics per zone and record type
Built on a globally distributed infrastructure, our service ensures high availability and fast propagation of DNS changes.
Core DNS Concepts
DNS Zone — a domain space where you manage records (e.g., example.com
)
SOA (Start of Authority) — the primary DNS record containing critical zone metadata (e.g., admin email, refresh intervals)
Nameservers (NS) — servers that handle DNS queries for your domain. Default nameservers: ns1-c.trbcdn.net.
, ns2-c.trbcdn.net.
, ns3-c.trbcdn.net.
.
FQDN (Fully Qualified Domain Name) — a complete domain name, including hostname, domain, and optional root dot (e.g., www.example.com.
)
Record Set — a group of records of the same type for a domain (e.g., multiple A records for sub.example.com
)
TTL (Time To Live) — how long (in seconds) DNS resolvers cache records before refreshing.
* Low TTL (e.g., 300s) → Faster updates, more queries * High TTL (e.g., 86400s) → Better caching, slower updates
Setting Up a DNS Zone
Step 1: Add a Zone
- Go to DNS Management in your dashboard
- Click "Add DNS-zone"
- Enter your domain (e.g.,
example.com
) - Click "Create"
Step 2: Configure Nameservers
After creation, assign these nameservers at your registrar:
ns1-c.trbcdn.net. ns2-c.trbcdn.net. ns3-c.trbcdn.net.
Attention
Propagation may take up to 24 hours.
Managing DNS Records
Adding a Record
- Select your zone
- Click "Add a set of recordings"
-
Configure:
- Type (
A
,AAAA
,CNAME
,MX
,TXT
, etc.) - Name (e.g.,
www
forwww.example.com
) - Value (IP, domain, or text)
- TTL (default: 3600s)
Common Record Types
Type Purpose Example A IPv4 address 192.0.2.1 AAAA IPv6 address 2001:db8::1 CNAME Domain alias shop.example.com MX Mail server 10 mail.example.com TXT Verification/SPF/DKIM v=spf1 include:_spf.example.com ~all - Type (
-
Click "Create"
Best Practices & Troubleshooting
- Verifying DNS Changes:
nslookup -type=A shop.example.com nslookup -type=MX example.com dig example.com SOA
- Propagation Times:
- First setup: Up to 24 hours
- Updates: Follows TTL (default: 1 hour)
- Clearing DNS Cache
- Windows:
ipconfig /flushdns
- macOS/Linux:
sudo dscacheutil -flushcache
- Windows:
- SOA Record Settings
Parameter | Purpose | Recommended Value |
---|---|---|
Refresh | How often secondary nameservers check for updates | 10800s (3h) |
Retry | Retry interval if update fails | 3600s (1h) |
Expire | Time until zone becomes invalid | 604800s (1 week) |
Minimum | Negative cache TTL | 3600s (1h) |
Tip
Lower TTL before major changes to speed up updates.
Need Help?
If DNS records aren’t working:
- Wait up to 24 hours for propagation.
- Double-check record values.
- Contact support if issues persist.
For advanced users:
- Use
dig
ornslookup
for debugging. - Monitor changes with DNS propagation tools (e.g., DNS Checker)