TL;DR DNS
DNS stands for Domain Name System and it is often described as the phone book of the internet. When you type a domain name like cloudsonic.com.au into your browser, your computer does not actually know where that website lives. It contacts a DNS server which looks up the domain name and returns the corresponding IP address of the server hosting that site. Your browser then connects to that IP address and loads the page. This lookup process happens in milliseconds and is invisible to the user. DNS also controls other records beyond just website addresses, including where your emails are delivered, whether your domain has security records like SPF and DKIM, and how traffic is routed through systems like Cloudflare Enterprise. CloudSonic manages DNS configuration for you as part of onboarding so you do not need to touch DNS settings manually.
How DNS Works
When you type a domain name into your browser, your computer first checks its local cache to see if it already knows the IP address for that domain. If not, it sends a query to a DNS resolver, usually provided by your internet service provider or a public service like Google's 8.8.8.8. The resolver checks its own cache and if it does not have the answer it begins a recursive lookup. It first contacts one of the internet's root nameservers which directs it to the nameserver responsible for the top-level domain, such as .com or .au. That nameserver directs it to the authoritative nameserver for the specific domain, which is where the actual DNS records are stored. The authoritative nameserver returns the IP address and the resolver passes it back to your browser, which then connects to that IP address and loads the page. This entire process typically takes between 20 and 120 milliseconds.
DNS records come in several types. An A record maps a domain to an IPv4 address. A CNAME record maps one domain name to another. MX records specify mail servers. TXT records are used for verification and security purposes including SPF and DKIM for email authentication. TTL, or Time to Live, controls how long DNS records are cached before a fresh lookup is required. When DNS is managed through Cloudflare Enterprise as it is on CloudSonic, DNS queries are resolved by Cloudflare's global network rather than a standard nameserver, which is significantly faster and adds an additional layer of security.
# Check what DNS records are set for a domain
dig cloudsonic.com.au ANY +short
# Check the A record specifically
dig cloudsonic.com.au A +short
# Check MX records for email routing
dig cloudsonic.com.au MX +short
# Check nameservers
dig cloudsonic.com.au NS +short
# Check TTL on a record
dig cloudsonic.com.au A +ttl
# Example zone file entries
cloudsonic.com.au. 300 IN A 203.0.113.42
www.cloudsonic.com.au. 300 IN CNAME cloudsonic.com.au.
cloudsonic.com.au. 300 IN MX 10 mail.cloudsonic.com.au.
cloudsonic.com.au. 300 IN TXT "v=spf1 include:_spf.cloudflare.com ~all"
Why DNS Matters for Your Website
DNS is the first step in every visit to your website and problems with DNS affect every visitor regardless of how fast your server is. If your DNS is slow, every page load starts with an avoidable delay before the browser can even begin connecting to your server. DNS lookup time contributes directly to TTFB and therefore to Core Web Vitals scores. If your DNS is unreliable or goes down, your website becomes unreachable even if your server is running perfectly. Visitors get DNS resolution errors and cannot reach your site at all. DNS is also a security surface. DNS hijacking and DNS spoofing attacks can redirect visitors to fraudulent versions of your site without touching your server. DNSSEC and DNS-level security features available through Cloudflare Enterprise protect against these attacks. Getting DNS right is foundational because every other performance and security improvement you make is irrelevant if visitors cannot resolve your domain reliably and quickly.
