Introduction
DNS records are the building blocks of the internet's addressing system. Every time someone visits your subdomain, sends an email, or connects to your server, DNS records translate human-readable names into network-usable addresses. Understanding these record types is essential for anyone managing online services. This guide explains each DNS record type in practical terms, with examples of how and when to use them with your is-pro.dev subdomain.
Prerequisites
- An is-pro.dev subdomain to practice with (free at dash.is-pro.dev)
- Basic understanding of how domain names and IP addresses work
- Access to a DNS dashboard (the is-pro.dev dashboard provides Cloudflare-powered DNS)
A and AAAA Records: Mapping Names to IP Addresses
An A record maps a domain or subdomain to an IPv4 address, such as 192.0.2.1. This is the most fundamental DNS record type — without it, your subdomain cannot point to a server. For example, if your VPS has an IP address of 203.0.113.5, you create an A record for myserver.is-pro.dev pointing to that IP. AAAA records do the same but for IPv6 addresses, which are longer (e.g., 2001:db8::1). Modern best practice is to include both A and AAAA records to support clients on either protocol. When setting up a web server, always verify that your A record resolves to the correct IP by using a DNS lookup tool.
CNAME Records: Aliasing One Name to Another
A CNAME record creates an alias from one domain name to another. For instance, www.is-pro.dev might be a CNAME pointing to is-pro.dev. CNAME records are essential for platforms like GitHub Pages, Vercel, and Netlify — you create a CNAME from your subdomain to the platform's provided domain. Important rules: a CNAME cannot coexist with other record types on the same name, and it cannot be used at the zone apex (the bare is-pro.dev domain). If you need the apex to alias to another domain, use an ALIAS or ANAME record if your provider supports it, or use CNAME flattening.
MX Records: Routing Email Delivery
MX (Mail Exchange) records specify which mail servers are responsible for receiving email on behalf of your subdomain. Each MX record has a priority value — lower numbers are tried first. For example, to receive email at hello@yourname.is-pro.dev, you configure MX records pointing to your email provider's servers. Cloudflare Email Routing uses MX records like route1.mx.cloudflare.net (priority 10) and route2.mx.cloudflare.net (priority 20). Always configure at least two MX records with different priorities for redundancy. Missing MX records mean email addressed to your domain will bounce or be undeliverable.
TXT Records: Storing Arbitrary Text Data
TXT records store text information associated with your subdomain. They are most commonly used for email authentication: SPF (Sender Policy Framework) records authorize which servers can send email from your domain, DKIM (DomainKeys Identified Mail) records provide cryptographic signatures, and DMARC (Domain-based Message Authentication, Reporting & Conformance) records specify how receivers should handle unauthenticated email. A typical SPF TXT record looks like: v=spf1 include:_spf.mx.cloudflare.net ~all. TXT records are also used for domain ownership verification — services like Google Workspace, AWS, or GitHub ask you to add a specific TXT record to prove you control the domain.
SRV Records: Locating Specific Services
SRV records generalize the concept of MX records to any service. They specify a target host and port for a specific protocol and service. The format is: _service._protocol.name TTL class SRV priority weight port target. For example, Minecraft game servers often use SRV records to point to a non-standard port: _minecraft._tcp.mc.is-pro.dev SRV 0 5 25565 mc-server.example.com. SRV records are also used by Discord for voice channels, Microsoft Teams for SIP services, and SIP-based phone systems. They are less common than A/CNAME records but critical for gaming and communication services.
Other Record Types: NS, CAA, PTR, and SOA
NS (Nameserver) records indicate which DNS servers are authoritative for a zone. For is-pro.dev subdomains, the NS records point to Cloudflare's nameservers and should not be modified. CAA (Certification Authority Authorization) records specify which certificate authorities are allowed to issue SSL certificates for your domain. Adding a CAA record for letsencrypt.org and cloudflare.com provides an extra security layer against unauthorized certificate issuance. PTR records (reverse DNS) map IP addresses back to domain names — they are managed by your hosting provider, not in your DNS dashboard. SOA (Start of Authority) records contain administrative information about the zone and are automatically managed.
Best Practices
- Always use DNS-only (gray cloud) for MX records — proxied MX records can interfere with email delivery
- Set TTL values based on how frequently you expect to change records: use 60 seconds during migration, 300-3600 seconds for stable configurations
- Add CAA records to restrict SSL certificate issuance to authorized providers only
- Use a DNS checker tool to verify each record type after making changes
Conclusion
DNS records form the foundation of how your subdomain interacts with the internet. Each record type serves a specific purpose, and knowing when to use A vs CNAME vs MX vs SRV is essential for configuring everything from websites to game servers. The is-pro.dev DNS dashboard, powered by Cloudflare, supports all standard record types and provides instant propagation across the global network.
FAQ
What is the difference between proxied (orange cloud) and DNS-only (gray cloud)?
Proxied routes traffic through Cloudflare's CDN, hiding your origin IP and providing DDoS protection. DNS-only passes traffic directly to your server. Use proxied for web servers, DNS-only for email and non-HTTP services.
Can I have multiple records of the same type for the same subdomain?
Yes, you can have multiple A records for load balancing (round-robin DNS), multiple MX records for redundancy, and multiple TXT records for different purposes (SPF, DKIM, DMARC).
How long does it take for DNS changes to take effect?
With Cloudflare DNS on is-pro.dev, changes typically propagate within seconds globally. The TTL value of the record determines how long clients cache the old value before rechecking.
FAQ
Is DNS setup free on is-pro.dev?
Yes, all subdomains on is-pro.dev include free DNS management and SSL certificates.
How long does DNS take to propagate?
Cloudflare typically propagates DNS changes within seconds to a few minutes globally.
Can I use this for commercial projects?
Yes, is-pro.dev subdomains can be used for personal and commercial projects within our fair use policy.