WordPress
WooCommerce
PHP Websites
Custom Websites
Hosting & Servers
Web Applications
DNS Records Explained: Types, Common Problems, and How to Manage Them
DNS (Domain Name System) is one of the fundamental technologies that makes the Internet accessible by connecting human-readable domain names to the servers and services behind them. Every time a user visits a website, sends an email, or accesses an online application, DNS records help route the request to the correct destination. Understanding DNS record types such as A, CNAME, MX, TXT, and NS records, along with concepts like nameservers, caching, TTL, and DNS management, is essential for website owners, developers, and IT professionals. This guide explains how DNS works, the most common DNS problems websites face, and how to manage DNS settings across popular platforms such as GoDaddy, Cloudflare, Shopify, Hostinger, and Namecheap.
1. What Is DNS?
DNS is one of the fundamental systems that makes the Internet easier to use. DNS translates human-readable domain names into information that computers can use to locate websites, email systems, applications, and other network services.
For example, a visitor may enter:
www.webkeepy.com
DNS helps determine which server or service should handle the request. In a simple website configuration, the DNS result may ultimately identify an IP address such as:
203.0.113.50
www.webkeepy.com
DNS lookup
IP address
Web server
Website
2. What Are DNS Records?
A DNS record is an individual instruction stored in a DNS zone. Different DNS record types perform different functions.
| Record | Purpose | Typical use |
|---|---|---|
| A | Maps a hostname to an IPv4 address. | Pointing a website to an IPv4 server. |
| AAAA | Maps a hostname to an IPv6 address. | Pointing a service to an IPv6 server. |
| CNAME | Creates an alias from one hostname to another hostname. | Pointing a subdomain to another hostname. |
| MX | Specifies mail servers responsible for receiving email. | Routing email for webkeepy.com. |
| TXT | Stores text information associated with a DNS name. | Domain verification, SPF, DKIM, and other services. |
| NS | Identifies the nameservers responsible for a DNS zone. | Delegating DNS authority. |
| SOA | Contains administrative information about a DNS zone. | Zone administration and DNS timing information. |
| SRV | Specifies the hostname and port for a particular service. | Specialized services such as SIP. |
| CAA | Controls which certificate authorities may issue certificates for a domain. | SSL/TLS certificate issuance control. |
3. How DNS Is Structured
DNS is organized hierarchically. At the highest level is the DNS root. Under the root are top-level domains, followed by individual domains and their DNS zones.
DNS Root │ ├── .com │ │ │ └── webkeepy.com │ ├── .org │ ├── .net │ └── other TLDs
For www.webkeepy.com, the domain belongs to the .com top-level domain, while webkeepy.com is the domain and www is the hostname.
4. Recursive DNS Resolvers
A recursive DNS resolver is a DNS server that performs DNS lookups on behalf of clients. Your device will normally ask a recursive resolver rather than contacting the root DNS servers directly.
The request can be thought of as:
Your device "What is the DNS information for www.webkeepy.com?" Recursive DNS resolver "I will find the answer."
The recursive resolver may already know the answer because it has a cached copy. If the answer is not cached, it can query the DNS hierarchy to obtain the information.
4.1 Where Recursive Resolvers Come From
A recursive resolver may be operated by:
- An Internet service provider
- A company or organization
- A public DNS provider
- A network administrator
- A local router or network service
5. Root DNS Servers
At the top of the public DNS hierarchy is the DNS root, represented conceptually by a single dot:
.
Root servers generally do not provide the final IP address for every website. Instead, they help the recursive resolver find the authoritative infrastructure responsible for a top-level domain such as .com.
For example, when resolving www.webkeepy.com, the recursive resolver can ask the root system where the .com infrastructure can be found.
6. TLD Nameservers
TLD means Top-Level Domain. Examples include .com, .org, .net, .az, and .uk.
For www.webkeepy.com, the TLD is .com.
TLD nameserver infrastructure helps the recursive resolver locate the authoritative nameservers for webkeepy.com.
7. Authoritative Nameservers
An authoritative nameserver is a server that provides the authoritative DNS information for a DNS zone.
A domain may use nameservers such as:
webkeepy.com Authoritative Nameservers: -------------------------- ns1.dns-provider.example ns2.dns-provider.example
These nameservers can contain the DNS records for the website, email services, verification systems, applications, and other services associated with webkeepy.com.
8. How a Recursive DNS Lookup Works
Suppose someone requests www.webkeepy.com.
- The device asks a recursive DNS resolver for information about
www.webkeepy.com. - The resolver checks whether it already has a valid cached answer.
- If there is no suitable cached answer, the resolver queries the DNS hierarchy.
- The root system identifies the appropriate TLD infrastructure.
- The TLD infrastructure identifies the authoritative nameservers for
webkeepy.com. - The authoritative nameserver provides the requested DNS record.
- The recursive resolver stores the result in its cache according to the record’s TTL.
- The resolver returns the result to the requesting device.
- The browser can then connect to the resulting destination.
Browser or device
Recursive DNS resolver
DNS root
.com TLD nameservers
Authoritative nameserver for webkeepy.com
Relevant DNS record
IP address or hostname
Web server or service
9. A Records
An A record maps a hostname to an IPv4 address.
For example:
webkeepy.com A 203.0.113.50
This associates webkeepy.com with the IPv4 address 203.0.113.50.
A DNS zone may contain several A records:
DNS Zone Records webkeepy.com TYPE: A VALUE: 203.0.113.50 api.webkeepy.com TYPE: A VALUE: 203.0.113.60 mail.webkeepy.com TYPE: A VALUE: 203.0.113.70
An AAAA record performs a similar function for IPv6 addresses.
10. CNAME Records
CNAME stands for Canonical Name. A CNAME creates an alias from one hostname to another hostname.
For example:
www.webkeepy.com CNAME webkeepy.com
The resolver can then look up webkeepy.com to determine its final DNS destination.
www.webkeepy.com
CNAME record
webkeepy.com
A or AAAA record
Final network destination
| Record | Example | Meaning |
|---|---|---|
| A | www.webkeepy.com → 203.0.113.50 | The hostname is mapped directly to an IPv4 address. |
| CNAME | www.webkeepy.com → webkeepy.com | The hostname is an alias for another hostname. |
The arrow characters in the table above are shown only as notation for mapping. They are not required in an actual DNS record.
11. TTL and DNS Caching
11.1 What Is TTL?
TTL means Time To Live. In DNS, TTL specifies how long a DNS answer may remain in a cache before it needs to be refreshed.
For example:
webkeepy.com A 203.0.113.50 TTL: 3600
A TTL of 3600 seconds is one hour.
TTL does not mean that the website stops working after one hour. It controls the lifetime of the cached DNS information.
11.2 Why DNS Uses Caching
Without caching, recursive resolvers would have to repeatedly query the DNS hierarchy for the same domain. That would create unnecessary traffic and additional delay.
With caching, a resolver can remember a DNS response for the duration permitted by the TTL.
DNS Response Domain: www.webkeepy.com IP Address: 203.0.113.50 TTL: 3600 seconds
During the cache period, a resolver may answer another request from its local cache instead of performing the entire lookup again.
11.3 Why DNS Changes Can Take Time
Suppose the DNS configuration originally contains:
webkeepy.com A 203.0.113.50
It is then changed to:
webkeepy.com A 203.0.113.80
A resolver may still have the previous value in its cache until the cached record expires.
12. Common DNS Problems Website Owners Face
12.1 Wrong A Record
If the A record points to the wrong IPv4 address, visitors may reach the wrong server.
Possible symptoms include:
- The wrong website appears.
- An old website appears.
- The connection times out.
- The domain reaches a server that does not host the intended website.
12.2 DNS Changes Are Not Visible Yet
A website owner may change a record and expect every user to see the new destination immediately. Cached DNS information can prevent the new result from appearing everywhere at the same time.
12.3 Incorrect CNAME
A CNAME can point to the wrong hostname, creating a broken subdomain or sending users to an unintended service.
For example, a subdomain might be configured to use a hostname that no longer exists.
12.4 Wrong Nameservers
This is one of the most important DNS management problems.
A website owner may make changes at one DNS provider while the domain’s authoritative nameservers still point to another provider.
DNS records edited at: Cloudflare Authoritative nameservers: GoDaddy Result: Cloudflare changes are not the active authoritative DNS configuration.
12.5 Accidentally Deleted Records
Deleting an important DNS record can break a website, email service, verification system, application, or another online service.
This frequently becomes a problem during hosting migrations and DNS cleanup.
12.6 DNS and SSL/TLS Problems
DNS and SSL/TLS are separate systems, but an incorrect DNS configuration can cause users to reach a server that does not have the correct SSL/TLS certificate.
This can produce browser errors related to certificate mismatches or HTTPS configuration.
12.7 Email Stops Working
DNS is also fundamental to email. A website owner can accidentally break email while making changes intended for the website.
Common email-related DNS records include:
- MX records for mail delivery
- TXT records for SPF and other verification
- DKIM-related DNS records
- DMARC-related DNS records
12.8 Incorrect AAAA Record
A domain may have both A and AAAA records. If the IPv4 configuration is correct but the IPv6 configuration points somewhere invalid, some users may have problems while others appear to have no problem.
12.9 DNSSEC Misconfiguration
DNSSEC adds cryptographic validation to DNS. Incorrect DNSSEC configuration can cause validating DNS resolvers to reject DNS information.
This can produce confusing situations where a domain works from one network but fails from another.
12.10 DNS Provider Outage
A DNS provider outage can prevent users from resolving a domain even when the web server itself is functioning.
DNS provider DNS resolution Website server
The website hosting server can be healthy while the domain remains inaccessible because users cannot obtain its DNS information.
12.11 Messy DNS Zones
DNS zones often become cluttered as a business adds hosting providers, email platforms, CDNs, marketing tools, SaaS services, verification records, and other integrations.
Old or unexplained DNS records make troubleshooting more difficult and increase the risk of accidental deletion.
12.12 Old Infrastructure
During migrations, some records may be updated while others continue pointing to old infrastructure.
DNS Migration Status Hostname Destination ------------------------------------------ webkeepy.com New server www.webkeepy.com Old server api.webkeepy.com Old server
This can create situations in which the main website works but a subdomain, API, or other service does not.
13. DNS Management and Authoritative Nameservers
One of the most important concepts in DNS management is understanding the difference between the domain registrar, DNS provider, and hosting provider.
13.1 Domain Registrar
The domain registrar is the company through which the domain is registered and managed.
13.2 DNS Provider
The DNS provider hosts and serves the authoritative DNS zone.
13.3 Web Hosting Provider
The web hosting provider runs the website or application.
13.4 Email Provider
An email provider handles mailboxes and email delivery.
These roles can all belong to different companies.
Website Infrastructure Domain registrar: Namecheap DNS provider: Cloudflare Website hosting: Hostinger Email provider: Google Workspace
14. Managing DNS with GoDaddy
When a domain uses GoDaddy’s authoritative nameservers, DNS records can be managed through the GoDaddy account. GoDaddy also emphasizes that DNS management depends on the nameservers being used.
GoDaddy DNS management documentation
A typical DNS zone may contain:
DNS Zone Records Type Name Value --------------------------------------- A @ 203.0.113.50 CNAME www webkeepy.com MX @ mail.provider.example TXT @ verification-value
GoDaddy supports common DNS record types such as A, AAAA, CNAME, MX, TXT, SRV, NS, and CAA.
15. Managing DNS with Cloudflare
Cloudflare is commonly used as an authoritative DNS provider and can also provide additional network and web infrastructure services.
A common architecture is:
Website DNS Architecture Domain registrar: Namecheap Authoritative nameservers: Cloudflare DNS management: Cloudflare Website hosting: Hostinger
Cloudflare’s DNS dashboard provides tools for creating, editing, and deleting DNS records. It also provides controls such as TTL and proxy status for supported records.
15.1 Cloudflare Proxy Status
Cloudflare introduces an important distinction between DNS-only and proxied traffic for supported services.
With DNS-only traffic, the user can connect to the destination identified by DNS.
With supported proxied traffic, the request can pass through Cloudflare before reaching the origin server.
DNS Only: Visitor | | DNS | | Origin server Proxied: Visitor | | Cloudflare | | Origin server
The proxied model allows Cloudflare to provide services associated with its network and web application infrastructure.
16. Managing DNS with Shopify
Shopify provides DNS management for domains that are managed through Shopify. Its DNS settings allow management of several common record types.
Shopify DNS settings documentation
The general management path is:
Shopify DNS Management Path Shopify Admin Settings Domains Select the domain DNS settings Manage
Shopify creates default DNS settings needed to connect a domain to a Shopify store.
16.1 Using a Third-Party Domain with Shopify
A domain does not need to be registered with Shopify to be used with Shopify.
For example:
Shopify Website Setup Domain registrar: Namecheap DNS provider: Namecheap or Cloudflare Website platform: Shopify
In this setup, DNS is configured at the active DNS provider according to Shopify’s connection requirements.
17. Managing DNS with Hostinger
Hostinger provides DNS management through hPanel and its DNS Zone Editor.
Hostinger DNS management documentation
The general workflow is:
Hostinger DNS Management Path Hostinger hPanel Domains or DNS DNS Zone Editor DNS records
Hostinger supports common record types such as A, AAAA, CNAME, MX, TXT, CAA, and SRV, depending on the service and configuration.
Hostinger also provides functionality such as DNS history and DNS import or export in supported configurations.
18. Managing DNS with Namecheap
Namecheap refers to DNS records in its Advanced DNS interface as Host Records.
The general path is:
Namecheap DNS Management Path Namecheap Domain List Manage Advanced DNS Host Records
Namecheap Host Records documentation
Namecheap Host Records are available when the domain is using Namecheap’s supported DNS services. If the domain uses third-party nameservers, DNS must be managed at the provider operating those nameservers.
A typical zone could contain:
DNS Host Records Type Host Value -------------------------------------------- A Record @ 203.0.113.50 CNAME www webkeepy.com MX Record @ mail.provider.example TXT Record @ verification-value
19. Comparing the Five Providers
| Provider | DNS management | Important consideration |
|---|---|---|
| GoDaddy | DNS management through the domain account | DNS is active there when GoDaddy nameservers are authoritative. |
| Cloudflare | Dashboard, DNS, Records | Often becomes authoritative after the domain uses Cloudflare nameservers; includes proxy controls. |
| Shopify | Settings, Domains, DNS settings | Shopify-managed domains have required records for the store connection. |
| Hostinger | hPanel and DNS Zone Editor | The active DNS zone depends on the authoritative nameservers. |
| Namecheap | Advanced DNS and Host Records | Host Records apply when Namecheap DNS services are being used. |
20. Registrar, DNS Provider, Hosting, and Email Provider
A practical website setup can use several different companies for different functions.
| Role | Purpose |
|---|---|
| Domain registrar | Registers and manages the domain. |
| DNS provider | Hosts and serves the authoritative DNS zone. |
| Web hosting provider | Hosts the website or application. |
| Email provider | Handles email delivery and mailboxes. |
| CDN or edge provider | Can sit between visitors and the origin server and provide caching, security, or traffic services. |
A realistic setup might be:
Website Infrastructure Service Provider -------------------------------------------- Domain registrar Namecheap DNS provider Cloudflare Website hosting Hostinger Email provider Google Workspace
21. The Most Important DNS Management Rule
Before editing DNS, determine:
- Who is the domain registrar?
- Which nameservers are configured for the domain?
- Which provider operates those nameservers?
- Where is the authoritative DNS zone managed?
- Which record needs to be changed?
- What service should that record point to?
22. Practical DNS Troubleshooting
When someone says, “My website is not working,” do not immediately assume that the web server or application is broken.
A structured troubleshooting process is:
- Check whether the domain resolves.
- Check which nameservers are authoritative.
- Check the A and AAAA records.
- Check CNAME records for relevant hostnames.
- Check whether the destination belongs to the correct server or platform.
- Check whether DNS caching or TTL is affecting the result.
- Check SSL/TLS configuration on the destination.
- Check the web server.
- Check the application itself.
Does the domain resolve?
Who is authoritative?
What DNS records are being returned?
Where do those records point?
Does the destination server respond?
Is HTTPS and SSL/TLS configured correctly?
Is the application working?
23. DNS Troubleshooting Tools
Once you understand DNS, you can inspect DNS directly rather than relying only on the provider’s dashboard.
23.1 Check an A Record
dig www.webkeepy.com A
23.2 Check Nameservers
dig webkeepy.com NS
23.3 Check a CNAME
dig www.webkeepy.com CNAME
23.4 Check Email Records
dig webkeepy.com MX
23.5 Use nslookup
nslookup www.webkeepy.com
These tools help answer a critical practical question:
What DNS information is actually being returned for www.webkeepy.com?
If you want to eliminate technical complexity and ensure your DNS servers are always fast, secure, and up-to-date, let our experts handle it for you. At WebKeepy, we offer complete hosting and server management—from initial configuration and performance tuning to 24/7 monitoring and proactive security patching. We support AWS, Google Cloud, VPS, shared hosting, and dedicated servers so you can focus entirely on growing your business.
24. A Simple Mental Model for DNS
24.1 Layer One: Determine DNS Authority
DNS Authority Structure Domain Nameservers Authoritative DNS provider
24.2 Layer Two: Read the DNS Records
Authoritative DNS DNS Records: A record AAAA record CNAME record MX record TXT record Other records
24.3 Layer Three: Follow the Destination
DNS Record Destination: IP address or hostname Connected service: Server or platform Used by: Website, email service, or application
25. Final Summary
DNS is the naming and service-discovery system that connects human-readable domain names such as www.webkeepy.com with IP addresses and other service information.
The most important concepts are:
- Recursive resolver: Finds DNS answers on behalf of clients and caches the results.
- Root servers: Help identify the appropriate TLD infrastructure.
- TLD nameservers: Help identify authoritative nameservers for domains.
- Authoritative nameservers: Serve the authoritative DNS records for a DNS zone.
- A record: Maps a hostname to an IPv4 address.
- AAAA record: Maps a hostname to an IPv6 address.
- CNAME record: Makes one hostname an alias for another hostname.
- MX record: Specifies mail servers for a domain.
- TXT record: Stores text information commonly used for verification and email security.
- TTL: Controls how long DNS information can remain cached.
- DNS caching: Reduces repeated DNS queries and improves efficiency.
- Nameservers: Determine which DNS infrastructure is authoritative for the domain.
Once these concepts are understood, managing DNS across GoDaddy, Cloudflare, Shopify, Hostinger, Namecheap, and other providers becomes much easier. The interfaces may differ, but the underlying DNS principles remain the same.