Got a JAMB or WAEC student at home? Free CBT practice, daily questions, and monthly cash rewards for top students on the WNG Student Hub.Practice Free

How to Check Your Domain’s DNS Records

How to Check Your Domain’s DNS Records

Community › Domain Names

Frank ApokwuezeWinig
1156 discussions | 33 replies

6 views

Here is a practical guide to how to check your domain’s DNS records, whether you are troubleshooting a website, email, SSL, domain connection, or hosting setup.

How to Check Your Domain’s DNS Records

DNS, or Domain Name System, records tell the internet where different services connected to your domain should go. For example, your A record can point your domain to a web server, while your MX records tell email providers where to deliver your emails.

You can check DNS records in several ways.

1. Check through your domain registrar

Log in to the company where you registered your domain. Look for something such as:

DNS Management
DNS Settings
Manage DNS
Zone Editor
Advanced DNS

You will usually see records such as:

Record Purpose
A Points a domain to an IPv4 address
AAAA Points a domain to an IPv6 address
CNAME Points one hostname to another hostname
MX Controls email delivery
TXT Stores verification and security information
NS Identifies the authoritative nameservers
SRV Defines certain service locations
CAA Controls which certificate authorities can issue SSL certificates

For example, an A record might look like:

example.com → 192.0.2.10

A CNAME might look like:

www.example.com → example.com

And an MX record might point to an email server such as:

mail.example.com

2. Check DNS using your computer

On Windows, open Command Prompt and type:

nslookup example.com

Replace example.com with your actual domain.

To check a particular record, you can use:

nslookup -type=A example.com

For MX records:

nslookup -type=MX example.com

For TXT records:

nslookup -type=TXT example.com

For nameservers:

nslookup -type=NS example.com

On macOS or Linux, you can also use:

dig example.com

Or:

dig A example.com

For email records:

dig MX example.com

For TXT records:

dig TXT example.com

3. Use an online DNS checker

You can also use an online DNS lookup service. Enter your domain name, select the record type you want to investigate, and the service will show the records that DNS resolvers can currently see.

This can be particularly useful when you have recently changed your DNS settings and want to determine whether the new records are visible publicly.

4. Check your nameservers first

One of the most important things to check is your domain’s NS records.

Your nameservers determine which DNS provider is actually controlling your domain’s DNS zone.

For example, your registrar might be one company while your DNS is managed somewhere completely different.

If your domain is using nameservers belonging to another provider, changing DNS records at your registrar may have no effect because the active DNS zone is elsewhere.

You can check this with:

nslookup -type=NS example.com

or:

dig NS example.com

5. Check your A record

If your website is not loading correctly, the A record is one of the first records to investigate.

Run:

nslookup -type=A example.com

The returned IP address should correspond to the server hosting your website.

If your hosting company gave you a specific IP address but DNS is returning a different address, your domain may be pointing somewhere else.

6. Check your CNAME record

If you use www, a subdomain, or a service such as a website platform, you may need to check your CNAME records.

For example:

nslookup -type=CNAME www.example.com

You might discover that:

www.example.com → example.com

or that it points to a third-party service.

7. Check your MX records

If your website works but your email does not, check your MX records.

Run:

nslookup -type=MX example.com

or:

dig MX example.com

Your MX records tell other mail servers where to deliver messages sent to addresses using your domain.

If you recently moved your email service, incorrect MX records can cause emails to go to the wrong provider or fail to arrive.

8. Check your TXT records

TXT records are commonly used for domain verification and email security.

Run:

nslookup -type=TXT example.com

You may find records associated with services such as Google, Microsoft, email authentication systems, website verification, or other platforms.

For email authentication, you may encounter records beginning with:

v=spf1

These are SPF records.

You may also encounter DKIM information, although DKIM is normally published under a special hostname rather than directly at the root domain.

DMARC is commonly found at:

_dmarc.example.com

You can check it with:

nslookup -type=TXT _dmarc.example.com

9. Remember that DNS changes may take time

One of the biggest mistakes beginners make is changing a DNS record and immediately assuming that it has not worked.

DNS information can be cached by different DNS resolvers. Consequently, you may temporarily see the old record from one location and the new record from another.

This is why checking your domain from more than one DNS resolver can be useful.

For example, you could compare what your computer sees with what a public DNS lookup service reports.

10. Be careful before deleting DNS records

Do not delete a DNS record simply because you do not recognise it.

A record that looks unimportant could be responsible for:

Your website
Your business email
Email authentication
SSL certificate validation
Domain verification
A subdomain
A third-party application
A payment or business service

Before modifying DNS, take a screenshot or copy the existing records somewhere safe.

A good habit is to document your DNS records before making major changes.

The simple beginner method

If you are completely new to DNS, start with these four checks:

NS → Who controls my DNS?
A → Where does my website point?
CNAME → What does my subdomain point to?
MX → Where does my email go?

Then investigate TXT, SPF, DKIM, DMARC, CAA and other records when necessary.

DNS can look complicated at first, but once you understand what each record controls, troubleshooting becomes much easier.

If your domain is connected to WordPress, hosting, Google Workspace, Microsoft 365, Cloudflare, or another service, the DNS records provided by that service should be compared with the records currently published for your domain.

 

Join the conversation. What is your own experience with this? Share your answer below, ask a follow-up question, or post what worked for you.
Frank Apokwueze
https://www.franklyntechnologies.com.ng

Frank Apokwueze is a technology enthusiast, website developer, SEO strategist, and digital business advocate passionate about helping individuals and businesses build a stronger presence online. Through Franklyn Technologies, he shares practical insights on website development, SEO, digital marketing, online business, and emerging technology to help readers understand and take advantage of the digital world.

Post a reply