When you register a domain, you’re creating your online address, with a fundamental part of your domain is DNS, which contains DNS records that make that address reachable. Sometimes, you need to check these records to ensure that they are configured correctly between your domain name and its corresponding IP address.
This guide will help you understand DNS records, why they matter, and how to check DNS records to make sure that they are configured correctly to maintain your website and email functionality.
- What Are DNS Records?
- Why DNS Records Matter
- Common DNS Record Types and Their Purpose
- DNS Records Explained
- What is a DNS Lookup?
- Forward vs. Reverse DNS Lookup Types
- How to Check DNS
- When Should You Update DNS Records?
- How to Update DNS Records
- DNS Propagation and Timing
- When to Contact 1-grid Support
- FAQs
- Additional Resources
What Are DNS Records?
Your website, email, subdomains, and many services all rely on DNS. A fundamental part of this is DNS records, which are instructions that tell the internet where to find your website, email, and other online services.
It’s like a digital address book or GPS that guides traffic for your domain.
Why DNS Records Matter
- They connect domain names to IP addresses.
- They ensure websites load, emails are delivered, and services like FTP and verification work.
- Incorrect DNS setup can cause websites to go offline or emails to bounce.
Common DNS Record Types and Their Purpose
DNS records are entries in the DNS system that define how your domain behaves, with each record type serving a specific function.
For Website Hosting, the A or CNAME record points your domain to the server’s IP.
For Email, the MX records define which servers receive your email; TXT records (SPF, DKIM) authenticate your messages and protect deliverability.
| Record Type | Purpose | Example |
| A Record | Points your domain to an IP address. | 192.0.2.1 |
| AAAA Record | Maps the hostname to a 128-bit IPv6 address of the given domain name. | 2001:db8::1 |
| CNAME Record | Points one domain name to another. | www → yourdomain.com mail.yourdomain.com |
| MX Record | Directs email to your mail server. | 1-grid-mx01.co.za 1-grid-mx02.com 1-grid-mx03.co.za 1-grid-mx04.com |
| TXT Record | Used for SPF, DKIM, domain verification, etc. | |
| SPF Record | Used to identify authorisation of sending on your domain to protect against spam. | v=spf1 include:relay.mailchannels.net ~all |
| DKIM Record | Used alongside an SPF record for email authentication. | |
| DMARC Record | Tells the domain what it should do in the event of an email failing the SPF and DKIM checks. | |
| NS Record | Used to identify the authorisation of sending on your domain to protect against spam. | thor.ns.1-grid.com thor.ns.1-grid.co.uk thor.ns.1-grid.co.za thor.ns.1-grid.net |
| CAA Record | Reflects the public policy regarding issuing digital certificates for the domain. | |
| SRV Record | Specifies a server for a specific service. | _sip._tcp → service URL and port |
| PTR Record | Reverse lookup to point the IPv4 or IPv6 address to its machine’s hostname. | |
| SOA Record | Stores admin information about the domain. |
IMPORTANT: When DNS records are missing, misconfigured or conflicting, email or website issues often follow.
DNS Records Explained
NS Record
Nameservers are a key part of the Domain Name System (DNS). They connect your domain (e.g., yourbusiness.co.za) to the server where your website and email are hosted (e.g., thor.ns.1-grid.com, thor.ns.1-grid.co.uk, thor.ns.1-grid.co.za, etc.). Nameservers make sure your domain points to the right place online.
A Record
An A record (Address Record) maps a domain or subdomain (like example.com or blog.example.com) to an IP address (e.g., 192.168.0.1). This allows users to access websites using easy-to-remember domain names instead of numerical IP addresses.
CNAME Record
A CNAME record (Canonical Name) points a domain or subdomain to another domain name rather than directly to an IP address. This simplifies updates; you only need to change the linked A record, and all CNAMEs pointing to it will automatically resolve to the new IP.
For Example:
www.example.com can point to example.com, or docs.example.com can point to ghs.google.com for Google Workspace services.
MX Record
An MX record (Mail Exchanger) directs email for a domain to its designated mail server. Similar to CNAMEs, MX entries must point to a domain name, not directly to an IP address. They also include a “priority” value, determining the order in which mail servers are contacted.
For Example:
We suggest the following for emails with us:
1-grid-mx01.co.za
1-grid-mx02.com
1-grid-mx03.co.za
1-grid-mx04.com
TXT Record
A TXT record (Text record) stores human-readable text for various purposes beyond directing traffic.
They are dynamic and commonly used for:
- Sender Policy Framework (SPF): Helps identify legitimate email senders from your domain, reducing spam and spoofing. More information is available on How to Set up SPF Records.
- DomainKeys Identified Mail (DKIM): Verifies email authenticity through cryptographic signatures, ensuring messages haven’t been tampered with and originated from a trusted source.
SRV Record
An SRV (Service) record directs one domain to another by specifying a particular destination port. These records facilitate routing specific services to designated locations, such as VOIP or instant messaging.
AAAA Record
The AAAA record is similar to the A record, allowing you to point the domain to an IPv6 address.
What is a DNS Lookup?
DNS lookup refers to mapping a domain name to its corresponding IP address. It involves the steps taken by the DNS system to resolve a domain name query and provide the IP address required to establish a connection with the desired server.
An Overview of How DNS Works
1. First, type yourdomain.com into your web browser.
2. Next, your device asks a DNS resolver to find the right IP address for that domain.
- This resolver is often provided by your Internet Service Provider (like Vodacom or Telkom) or by a public service (like Google DNS 8.8.8.8 or Cloudflare 1.1.1.1).
3. Then, the resolver checks its memory (cache) to see if it already knows where that domain points.
- If it does, it quickly returns the saved result.
IMPORTANT: Because of caching, changes to DNS mean that DNS propagation can take time globally, which can be between 2 to 48 hours.
Forward vs. Reverse DNS Lookup Types
Forward DNS Lookup
Involves searching for the IP Address associated with a given domain name. This type lets you input your domain name and obtain the corresponding IP addresses.
Reverse DNS Lookup
This is used to identify the domain name associated with a given IP Address. Email servers commonly employ this lookup method to verify the legitimacy of recipients.
How to Check DNS
Control Panel DNS Zone Editor
We have some easy-to-understand, quick guides to help you navigate to your domain’s Zone Editor via your Control Panel with us, but here are some quick general steps:
- Log in to your 1-grid account and open cPanel / Plesk Control Panel.
- Go to Zone Editor.
- Select your domain and view existing records (A, MX, CNAME, TXT, NS).
- Confirm that they match the DNS values expected by 1-grid.
- If you see missing or incorrect records, you can edit them here as well.
DNS Checking Tools
- Use tools like DNSChecker.org, WhatsMyDNS.net, or MXToolbox.
- Enter your domain and select the record type you want to check.
- The tool will show results from many locations, helping you detect whether records are properly visible globally.
- If some servers still show old values, propagation may still be underway.
Command-Line Tools
On Windows (using Command Prompt):
- nslookup yourdomain.com → shows A record
- nslookup -type=MX yourdomain.com → shows MX records
- nslookup -type=TXT yourdomain.com → shows TXT (SPF / DKIM)
On Linux / macOS (using dig):
- dig yourdomain.com
- dig MX yourdomain.com
- dig TXT yourdomain.com
These commands let you confirm whether records have been published globally.
IMPORTANT: You should replace “domain.com” with the website (domain) for which you want to perform the lookup. Moreover, change “recordtype” with the record types like A, AAAA, CNAME, MX, etc.
When Should You Update DNS Records?
You may need to update DNS records when:
- Pointing your domain to a new website host.
- Setting up third-party email providers like Google Workspace or Microsoft 365.
- Adding custom records for services like Shopify.
How to Update DNS Records
When updating your DNS records, it is important to take a screenshot or export your existing DNS records before making changes in case you need to revert.
To update your DNS records, please check out our quick guides for easy-to-follow instructions to make the process simple.
DNS Propagation and Timing
Changes to DNS don’t take effect everywhere instantly. Because of caching at ISP/Host resolvers, some users may still see the old record for up to 2 to 48 hours. Be patient and avoid making repeated live updates too quickly to allow propagation to complete fully.
When to Contact 1-grid Support
If, after verifying your DNS records and waiting for propagation, your website or email still fails:
- Provide your domain name and current DNS records.
- Describe the issue (email failure, website not loading, with screenshots, where possible).
- Note any recent DNS changes you made.
FAQs
Can I use both A and CNAME for the same record?
No, you should choose one if you use one hostname. An A record points directly to an IP; a CNAME is an alias to another name so don’t mix them for the same hostname.
Do I need both MX and TXT records for email?
Yes, MX directs mail delivery, while TXT is often used for SPF, DKIM, and DMARC authentication.
Why is my DNS change not visible instantly?
Because DNS caches across the internet must expire (TTL). It can take up to 48 hours for full propagation.
Will DNS misconfiguration affect both website and email?
Yes, if A, MX or related records are wrong, both your website and email can malfunction.
What does “TTL” mean, and why does it matter?
TTL (Time To Live) defines how long DNS records are cached before refreshing. Lower TTLs let changes propagate faster.
Why do some DNS Checkers show the old record?
Those servers haven’t yet updated their cache, and DNS propagation varies by location.
Can I break my site by deleting a record?
Yes, deleting an A, MX, or NS record can disrupt your website or email so always make note of your DNS before editing.
Is there a limit to how many DNS records I can have?
No, there’s no strict limit, but too many can slow down lookups. Only include what you need.
How long should I wait before assuming something is wrong?
Usually 24 to 48 hours due to propagation timing. If issues persist beyond that, investigate or contact support.
Additional Resources
DNS Explained Video
Understanding DNS, Its Record Types and How It Works
DNS Propagation and Why It Takes So Long
Everything You Need to Know About Domains at 1-grid
How to Enable DKIM and SPF on Your Mail Domain
Why SSL? The Purpose of Using SSL Certificates
How to Update Your Domain’s Nameservers at 1-grid
Settings to Configure Your 1-grid Email Accounts Across Devices
How to Set Up Email on Android for Your 1-grid Email Accounts
Setting Up Email in Outlook via Windows Control Panel
Troubleshooting Steps for Email
Email Error Messages: What Do They Mean and How to Fix Them
Top 10 Common Email Issues and How to Resolve Them
What Is Email Spoofing? How It Works and How to Protect Yourself
How to Spot a Scam Email
Email Headers FAQs
Email FAQs
MailChannels FAQs
SpamTitan FAQs
Need Additional Support?
We’re Here to Help:
Understanding DNS records and how they work doesn’t have to feel technical with this easy-to-understand guide. Stuck? Contact our Support Team for clarity and guidance (https://1grid.co.za/contact-us/). We’re ready to see how we can help!