Understanding DNS and Nameservers
Overview
DNS, or the Domain Name System, is one of the fundamental systems that makes the internet work.
When you type a domain name such as:
example.com
into your browser, your computer needs to determine which server should receive that request.
DNS provides that information.
If you're new to hosting, DNS can seem complicated at first. Fortunately, you don't need to understand every technical detail to use your Have Freedom Hosting account.
This guide explains the basics of DNS, nameservers, and the most common types of DNS records you'll encounter.
What Is DNS?
DNS stands for Domain Name System.
Its primary purpose is to translate human-readable domain names into information that computers and internet services can use.
Think of DNS like the internet's address book.
Instead of requiring visitors to remember a numerical IP address such as:
203.0.113.25
they can simply visit:
example.com
DNS helps direct that request to the appropriate destination.
What Are Nameservers?
Nameservers are DNS servers that tell the internet where the DNS information for your domain is managed.
For example, a domain may use nameservers such as:
ns1.example.com
ns2.example.com
The nameservers don't necessarily point directly to your website.
Instead, they tell DNS resolvers where to find the DNS records that contain the instructions for your domain.
A simplified example looks like this:
Your Domain
↓
Nameservers
↓
DNS Records
↓
Website / Email / Other Services
Nameservers vs. DNS Records
These two terms are often confused.
Nameservers
Nameservers tell the internet:
"This is where the DNS information for this domain is managed."
DNS Records
DNS records tell the internet:
"This is what this particular hostname or service should do."
For example, an A record might tell DNS where your website is hosted, while an MX record tells email systems where to deliver your email.
Common DNS Records
You may encounter many different types of DNS records. The following are some of the most common.
A Record
An A record points a hostname to an IPv4 address.
For example:
example.com → 203.0.113.25
A records are commonly used to direct a website to a hosting server.
AAAA Record
An AAAA record performs a similar function to an A record, but points to an IPv6 address.
For example:
example.com → 2001:db8::1
Not every website needs to be manually configured with an AAAA record.
CNAME Record
A CNAME record points one hostname to another hostname.
For example:
www.example.com → example.com
CNAME records are commonly used for subdomains and services that provide a hostname instead of a fixed IP address.
MX Record
An MX, or Mail Exchange, record tells mail servers where email for your domain should be delivered.
For example:
example.com → mail.example.com
MX records are particularly important when using domain-based email.
If your domain's MX records are incorrect, email may not be delivered correctly.
TXT Record
A TXT record stores text-based information associated with a domain.
TXT records are commonly used for things such as:
-
Domain verification
-
Email authentication
-
SPF
-
DKIM-related configuration
-
Service verification
-
Other security and configuration requirements
A TXT record may look complicated because the value stored inside it can be quite long.
Important: Don't change or delete an unfamiliar TXT record without knowing what it is used for. It may belong to an important service.
How DNS Connects Your Domain to Your Website
When someone enters your domain into their browser, several things happen behind the scenes.
A simplified version looks like this:
1. Visitor enters your domain
example.com
↓
2. DNS lookup occurs
The visitor's device or DNS resolver looks up the domain's DNS information.
↓
3. DNS provides the appropriate destination
For example, an A record may provide the IP address of your hosting server.
↓
4. The browser connects to the server
The visitor's browser connects to the appropriate hosting server.
↓
5. Your website is delivered
The server sends the requested website content back to the visitor.
All of this generally happens within seconds.
How DNS Works With Email
DNS isn't only used for websites.
It also plays an important role in email.
When someone sends a message to:
the sending mail server needs to determine where mail for example.com should be delivered.
It checks the domain's MX records to determine which mail server is responsible for receiving the message.
This means that your website and email can use the same domain while being hosted by completely different services.
For example:
Website → Have Freedom Hosting
Email → Another email provider
This is possible because DNS lets you configure the services independently.
Using Have Freedom Hosting Nameservers
If you're using Have Freedom Hosting's nameservers, your domain's DNS is generally managed through the DNS infrastructure associated with your hosting service.
This can simplify management because your website and other hosting-related DNS records can be managed in one place.
When using Have Freedom Hosting nameservers, use the exact nameserver addresses provided with your hosting service.
Never guess your nameservers. Use the values provided by Have Freedom Hosting for your account.
Using a Third-Party DNS Provider
You don't have to use Have Freedom Hosting's nameservers.
You may instead choose to manage DNS through another provider.
For example, some customers may use a third-party DNS service for additional DNS management, security, performance, or other features.
If you do this, your DNS records must be configured correctly to point your website and other services toward their respective destinations.
In this situation, Have Freedom Hosting may provide the information you need, such as:
-
Server IP address
-
Hostname
-
Required DNS records
-
Email-related DNS information
-
Other service-specific configuration
What Is DNS Propagation?
When you change DNS information, the change isn't necessarily visible everywhere immediately.
DNS information is cached by many systems across the internet.
After a change, some systems may continue using the previous information until their cached data expires.
This process is commonly referred to as DNS propagation.
During this period, you may see inconsistent results.
For example:
-
Your website works on one device but not another.
-
Your old website is still visible from some locations.
-
Your new website appears from some networks but not others.
-
Some DNS lookup tools show the new records while others still show the old records.
This doesn't necessarily indicate a problem.
DNS TTL
You may encounter the term TTL, which stands for Time to Live.
TTL determines how long DNS information may be cached before it needs to be retrieved again.
For example, if a record has a TTL of one hour, a DNS resolver may cache that information for approximately that period before checking again.
TTL values can affect how quickly DNS changes become visible.
You generally don't need to change TTL values unless you have a specific reason to do so.
Changing DNS Safely
DNS changes can affect multiple services at the same time.
Before changing your DNS, consider what your domain currently uses.
For example:
-
Website
-
Email
-
Subdomains
-
Verification services
-
Security services
-
Third-party applications
-
Other domain-based services
If you're moving your website but keeping email somewhere else, changing nameservers without recreating the necessary email records can interrupt your email service.
Important: If your domain is already being used for email or other important services, document your current DNS configuration before making major changes.
Should I Change My Nameservers or DNS Records?
That depends on what you're trying to accomplish.
Change Nameservers When:
You want another provider to become responsible for managing your domain's DNS.
For example, you may want Have Freedom Hosting to manage the DNS for a domain you're hosting with us.
Change DNS Records When:
You want to change where a specific service points without moving all DNS management to another provider.
For example, you might change an A record for your website while keeping your email and other DNS settings with the same provider.
If you're unsure which option you need, ask before making the change.
Common DNS Problems
My Website Doesn't Load After Changing DNS
Verify that:
-
Your domain is active.
-
The correct nameservers are configured.
-
The appropriate DNS records exist.
-
Your hosting account is active.
-
The DNS change has had enough time to propagate.
My Website Works, but My Email Doesn't
Check your domain's MX records and other email-related DNS records.
Changing nameservers can remove or replace DNS records that your email provider depends on.
My Website Works for Me but Not Someone Else
This can happen while DNS changes are propagating or because different DNS resolvers have different cached information.
Give the change time to propagate before making additional changes.
I Don't Know What DNS Records I Need
Don't guess.
The correct records depend on the services you're using.
If you're connecting a domain to Have Freedom Hosting, the appropriate setup information should come from your hosting service or the service you're configuring.
Important DNS Safety Tips
DNS settings can affect your website, email, and other services.
When making DNS changes:
-
Make one change at a time when possible.
-
Double-check hostnames and IP addresses before saving.
-
Don't delete records simply because you don't recognize them.
-
Keep a record of your existing DNS configuration before making major changes.
-
Don't repeatedly change settings while waiting for propagation.
-
Ask for help if you're unsure what a record does.
A single incorrect DNS record can prevent a website from loading or cause email delivery problems.
Need Help?
If you're unsure about a DNS or nameserver change, Have Freedom Hosting Support can help you understand what information is needed.
When contacting support, provide:
-
Your domain name
-
What you're trying to accomplish
-
Where your domain is registered
-
Where your DNS is currently managed
-
Any DNS changes you've already made
-
The error or behavior you're experiencing
Never provide your domain registrar password, hosting password, email password, or other sensitive credentials in a support ticket.
DNS changes can have a significant effect on your website and email, so it's better to ask before making a change you're unsure about.
