registrar – AXR Global

If you have this problem—your website is down, your domain does not resolve, or business email suddenly stops arriving—the cause may not be your hosting plan or website code. In many cases, the problem is DNS.

DNS connects your domain to the servers that host your website and email. When a record is missing, a nameserver points to the wrong provider, or a recent change has not completed propagation, visitors may see an error while your email quietly bounces in the background.

For small business owners managing their own hosting, DNS can feel unnecessarily technical. The good news is that most DNS issues follow predictable patterns. Once you understand the difference between a registrar, a nameserver, and a DNS record, you can diagnose many problems yourself without having to wait for support.

This guide covers the most common DNS and nameserver problems, how to troubleshoot them step by step, and what to consider when choosing between registrar-managed DNS and DNS managed through your hosting provider.

What DNS and Nameservers Actually Do

Think of the internet like a city. Your domain is the street address people remember, such as yourbusiness.com. Your hosting server is the building where your website lives. DNS is the directory that tells browsers which building to visit.

When someone types your domain into a browser, the request follows a chain:

The domain is registered through a registrar.
The domain is connected to one or more nameservers.
Those nameservers publish DNS records.
The records direct traffic to your website, email provider, or other services.

A nameserver is not the same thing as a DNS record. The nameserver tells the internet where the instructions for your domain are stored. The records themselves contain the actual instructions:

An A record points a domain to an IPv4 address.
An AAAA record points a domain to an IPv6 address.
A CNAME record points one hostname to another, such as www to your root domain.
An MX record tells email services where to deliver messages.
A TXT record stores verification and email security information.

This distinction matters because a domain can be correctly registered while its nameserver configuration is wrong. Likewise, the nameserver can be correct while a single A, CNAME, or MX record is misconfigured.

For example, your registrar may show that yourbusiness.com is active, but the domain may still point to the nameservers of a former hosting provider. In that situation, the domain exists, but visitors are being directed to the wrong DNS instructions.

Five Common DNS Problems and How to Fix Them

1. DNS Propagation Hasn’t Finished

DNS propagation is the period during which DNS resolvers around the world refresh their cached responses after a change. If you recently switched nameservers, moved your website, or edited an A record, not every visitor will see the new destination immediately.

Many changes appear within minutes or a few hours. However, some resolvers may continue serving cached information for up to 24–72 hours, depending on the previous TTL and the type of change.

During propagation, two visitors may see different versions of the same domain:

One reaches the new hosting server.
Another still reaches the old server.
A third receives a temporary error.
Some email systems may continue seeing the previous MX records until their cached DNS information expires.

This does not necessarily mean the configuration is wrong. It may simply be too early to judge the result.

To verify propagation, use a public DNS checker or domain lookup tool and compare results from different locations. You can also inspect individual records with dig:

dig yourdomain.com A
dig yourdomain.com NS
dig yourdomain.com MX

On Windows, use:

nslookup yourdomain.com

If different resolvers return different values, the change may still be propagating. Avoid repeatedly editing the same record while you wait, because each new change can make the situation harder to diagnose.

2. Nameservers Point to the Wrong Place

A nameserver problem is one of the most disruptive DNS issues because it can affect the entire domain at once. If your domain points to nameservers from an old hosting provider, the internet consults the wrong DNS zone entirely.

This commonly happens after:

Moving to a new host.
Transferring a domain between registrars.
Cancelling an old hosting account.
Rebuilding DNS manually.
Setting up a CDN or security service.
Forgetting to update nameservers after a migration.

To fix the problem, first identify which provider should control your DNS. Your hosting company may provide nameservers such as:

ns1.examplehost.com
ns2.examplehost.com

An independent DNS service may provide a different pair. Compare the correct values with the nameservers currently listed in your registrar account.

Before changing nameservers, export or copy your existing DNS records. Make sure the new DNS provider has the records required for your website, email, subdomains, verification tools, and third-party services. A nameserver change can affect all of these at once.

3. A, CNAME, or MX Records Are Incorrect

Even when nameservers are correct, individual records can send traffic to the wrong destination.

An A record usually connects the root domain to an IP address:

yourbusiness.com → 203.0.113.10

A CNAME may connect www to the root domain or to a platform-managed hostname:

www.yourbusiness.com → yourbusiness.com

An MX record controls email delivery. If MX records are missing, incorrectly prioritized, or still point to an old provider, your domain name email may not arrive. Messages may bounce even though the website loads normally.

Before troubleshooting email, check:

Whether the MX records match your email provider’s instructions.
Whether the correct priority values are being used.
Whether an old MX record is still active.
Whether the root domain and www hostname use the intended values.
Whether your provider requires SPF, DKIM, or DMARC records.
Whether any required TXT verification records are present.

For Cloudflare DNS setups, keep mail-related hostnames configured according to your email provider’s instructions. MX records cannot be proxied, and hostnames used directly by mail services should generally remain DNS-only. Website records may use proxy features where appropriate, but do not apply the same setting automatically to every record.

To check your MX records, run:

dig yourdomain.com MX

For a browser-based alternative, use a public DNS lookup tool and search for the MX record type.

4. TTL and DNS Caching Create Confusing Results

TTL, or time to live, controls how long a DNS result can remain cached before a resolver checks again. A high TTL can reduce repeated DNS queries, but it also means that changes may remain invisible to some users for longer.

For example, if an old record had a TTL of 86,400 seconds, or 24 hours, some resolvers may continue using that cached value for up to a day. Changing the record does not instantly erase every cached copy across the internet.

Cache-related symptoms include:

The website works on your phone but not on office Wi-Fi.
A private browser window shows a different result.
Your mobile connection reaches the new server while another network reaches the old one.
A public DNS checker reports a mixture of old and new addresses.

Test the domain from more than one network before assuming that the DNS record is incorrect. You can use a second internet connection, a public DNS lookup tool, or a domain lookup service that checks multiple locations.

On Windows, you can clear the local DNS cache with:

ipconfig /flushdns

Clearing your local cache will not change cached results held by internet service providers or public resolvers, but it can help determine whether the issue is limited to your own device.

5. The Registrar and DNS Manager Are Being Confused

Your registrar is the company through which you register and renew your domain. DNS management is the interface where you edit nameservers and DNS records. These services may be offered by the same company, but they are separate functions.

A registrar typically handles:

Domain registration.
Renewal and expiration.
Domain transfers.
Contact information.
Transfer locks and authorization codes.

A DNS manager typically handles:

A, AAAA, CNAME, MX, and TXT records.
Nameserver configuration.
TTL values.
Subdomains.
Verification records.
DNS-based routing or security features.

You can register a domain with one company and manage DNS through another. That flexibility can be useful, but it also creates more places where a setting may be overlooked.

When comparing registrars, look beyond the introductory price. Check:

Renewal pricing.
Transfer policies.
DNS management features.
Support availability.
Domain privacy options.
Ease of exporting or editing DNS records.
Restrictions for the domain extension you plan to use.

The cheapest domain name registration offer may not provide the lowest long-term cost if renewal fees are high or DNS support is difficult to use.

Registrar Changes: Nameservers, Domain Transfers, and Propagation

Moving a domain between registrars is different from moving its website. A registrar transfer changes who manages the registration; it does not necessarily move your hosting files, website, or email.

Before transferring a domain:

Confirm that it is not inside a transfer lock period.
Make sure the domain is active and not close to expiration.
Record your current nameservers and DNS records.
Verify that your website and email work before starting.
Review the renewal price, not just the transfer promotion.
Confirm that the new registrar supports the features you need.

In many cases, nameservers remain unchanged during a registrar transfer. However, problems can occur if the new registrar resets them to default values or if your DNS was hosted inside the old registrar account.

If possible, avoid changing your registrar, hosting provider, nameservers, and email service at the same time. Making one change at a time makes propagation and troubleshooting much easier.

After the transfer, re-check:

The domain status.
The nameserver values.
The A and CNAME records.
The MX records.
SPF, DKIM, and DMARC records.
Website and email delivery.

If you also changed hosting or DNS providers, give the change enough time to refresh before assuming that the transfer failed.

Registrar-Managed DNS vs. Hosting-Managed DNS

There is no universally best option. The right setup depends on how often you change DNS, how complex your website is, and how much technical work you want to handle yourself.

	Registrar-Managed DNS	DNS Managed Through Your Host
Setup	Managed in the registrar’s dashboard, often with basic controls	Usually integrated with your website and hosting setup
Change speed	Depends on the provider’s DNS platform and TTL settings	Also depends on the provider’s DNS platform and TTL settings
Email handling	Often manual, so MX and TXT records must be entered carefully	May be auto-configured with hosting or email plans
Troubleshooting	You may need to coordinate between registrar and host	One support team may handle server and DNS questions
Flexibility	Useful if you change hosting providers frequently	Convenient when your website, server, and DNS stay together
Best for	Owners who want domain and DNS in one account	Businesses that prefer fewer moving parts

Neither option is automatically better. Registrar-managed DNS may be useful when you want to keep DNS independent from hosting. Hosting-managed DNS may be more convenient when the same provider manages your website, email, server, SSL certificate, and migration.

The most important factor is whether the setup is clear and easy to maintain. A simple DNS dashboard with reliable support is often more valuable than a long list of advanced features.

DNS Troubleshooting: Steps and Checklist

Use this process before changing several settings at once:

Define the symptom. Is the entire website down, only www, or just email?
Check domain status. Confirm that the domain has not expired and is active at the registrar.
Check nameservers. Run dig yourdomain.com NS or use a public domain name lookup tool.
Check A and CNAME records. Compare them with the information from your current host.
Check MX records. Compare them with your email provider’s exact instructions.
Check propagation. Test the domain from more than one network or location.
Consider TTL and caching. The old value may still be stored by a resolver.
Review recent changes. Look at hosting moves, registrar transfers, CDN setup, and email migrations.
Change one thing at a time. Wait for the result before editing another record.
Contact support with evidence. Include the domain, affected service, recent changes, and DNS results.

Use this checklist before opening a support ticket:

[ ] The domain is active and has not expired.
[ ] Nameservers at the registrar match the DNS provider.
[ ] The A record points to the current hosting IP.
[ ] CNAME records do not conflict with other records.
[ ] MX records point to the current email provider.
[ ] Required SPF, DKIM, DMARC, and TXT records are present.
[ ] The website has been tested on more than one network.
[ ] Enough time has passed for propagation.
[ ] No old hosting or email records remain active.
[ ] The registrar’s renewal pricing and transfer policies are understood.

DNS FAQ for Small Businesses

Why is my domain not resolving?

The most common causes are incorrect nameservers, a missing A record, an expired domain, or incomplete propagation after a DNS change. Check the domain status first, then compare the published nameservers and A record with your hosting provider’s information.

How long does DNS propagation take?

Many changes appear within minutes or a few hours. However, some resolvers may continue serving cached information for up to 24–72 hours, depending on TTL values, previous records, and the type of DNS change.

Nameserver vs. registrar — what’s the difference?

The registrar manages your domain’s registration, renewal, and transfer. The nameserver identifies where the domain’s DNS instructions are stored. A registrar may provide nameserver and DNS tools, but the two roles are not the same.

Should I use Cloudflare DNS?

Cloudflare DNS may be useful if you want to manage DNS separately from your registrar or need features such as Cloudflare Dynamic DNS for devices with changing IP addresses. It adds another account and configuration layer, however, so it is not necessary for every small business. Choose the setup you can maintain accurately.

Why doesn’t my domain name email work?

Check the MX records first. They may be missing, outdated, incorrectly prioritized, or still pointing to a previous email provider. Also confirm that the required TXT records are present and that your email provider has completed its setup process.

Is free domain name and hosting a good option?

Free domain name and hosting can work for testing or personal projects, but small businesses should review renewal terms, DNS access, support quality, storage limits, branding restrictions, and email capabilities. A low starting price is not always the best long-term value.

Need Help With Domain and DNS Migration?

DNS troubleshooting is manageable for many website owners, but a migration is a poor time to experiment. A small mistake in your nameserver or MX records can interrupt both your website and business email.

AXR Global helps businesses troubleshoot and plan changes involving hosting, domain registrars, DNS, and website migrations.

Contact us for a consultation if you need to troubleshoot your current setup, plan a DNS or hosting migration, or decide where your domain and DNS should be managed.

How to Prevent Future DNS Problems

Most DNS problems come down to a handful of predictable causes: incomplete propagation, a nameserver pointing to the wrong place, a misconfigured record, or a caching delay.

With a few free tools and a clear checklist, many small business owners can identify—and often fix—these issues without outside help. When comparing registrars or deciding where to manage DNS, reliability, renewal pricing, support, and ease of use usually matter more than the cheapest introductory offer.

Etiqueta: registrar

Common DNS Issues and How to Troubleshoot Them: A Registrar & Nameserver Guide