How to Fix WordPress DNS and Domain Configuration Problems

Is your WordPress website not loading correctly even though your hosting account and WordPress installation appear to be working?

DNS and domain configuration problems can be surprisingly difficult to diagnose. Your website may show an error in the browser, load the wrong website, work without www but not with it, redirect endlessly, or suddenly stop working after a hosting migration.

In many cases, WordPress itself is not the problem. The issue can be somewhere between your domain registrar, DNS provider, hosting server, SSL configuration, and WordPress settings.

This makes DNS problems particularly frustrating because a small configuration mistake can prevent visitors from reaching your entire website.

The good news is that most WordPress DNS and domain problems can be diagnosed systematically. Once you understand which part of the connection is failing, you can usually identify the problem without changing random WordPress settings or reinstalling anything.

This guide explains how to troubleshoot the most common WordPress DNS and domain configuration problems, including incorrect DNS records, domains pointing to the wrong server, www issues, SSL conflicts, Cloudflare configuration, redirect loops, DNS propagation, and problems that appear after moving WordPress to a new host.

What Is DNS and How Does It Work With WordPress?

DNS, or Domain Name System, connects your domain name to the server where your website is hosted.

When someone enters:

example.com

their browser needs to determine which server should receive that request.

DNS records provide that information.

For a typical WordPress website, the basic connection looks like this:

Domain → DNS records → Hosting server → WordPress website

If one part of that chain is configured incorrectly, the website may not load.

For example, your domain could still be registered correctly, while its DNS records point to an old hosting account. Your WordPress installation may be completely functional, but visitors will still be sent to the wrong server.

This is why it is important to separate WordPress problems from DNS and domain problems.

Common WordPress DNS and Domain Problems

Some of the most common issues include:

• Domain pointing to the wrong hosting server
• Incorrect A record
• Missing or incorrect www record
• Old DNS records remaining after a hosting migration
• Incorrect nameservers
• IPv6 AAAA record pointing to the wrong server
• Website showing the wrong hosting account
• ERR_NAME_NOT_RESOLVED
• DNS_PROBE_FINISHED_NXDOMAIN
• ERR_TOO_MANY_REDIRECTS
• SSL errors after changing DNS
• Cloudflare DNS configuration problems
• Domain working on one device but not another
• WordPress URL settings not matching the actual domain
• DNS propagation after changing hosting
• Domain forwarding interfering with the website
• Email stopping after changing nameservers
• DNSSEC configuration problems

The important thing is not to change everything at once.

Start by identifying where the connection breaks.

1. Check Where Your DNS Is Managed

The first step is determining which service currently controls your DNS records.

Your domain may be registered with one company while DNS is managed somewhere else.

For example:

Domain registrar: Company A
DNS: Cloudflare
Hosting: Company B

In this situation, changing DNS records inside the hosting account may have no effect if Cloudflare is actually managing the domain’s DNS.

Look at the nameservers assigned to your domain.

If they belong to Cloudflare, your DNS records need to be managed in Cloudflare.

If they belong to your domain registrar, the records may need to be changed there.

Why This Matters

A common mistake is changing DNS records in the wrong dashboard and assuming the changes should immediately fix the website.

Before changing anything, identify:

• Where the domain is registered
• Which nameservers are active
• Where DNS records are managed
• Which server currently hosts WordPress

Once you know those four things, troubleshooting becomes much easier.

2. Check Your Domain’s A Record

The A record is one of the most important DNS records for a typical WordPress website.

It tells the domain which IPv4 address should receive the traffic.

For example:

example.com → 203.0.113.10

The IP address needs to match the server where your website is hosted.

If the A record points to an old hosting server, visitors may see:

• An old version of the website
• A hosting provider’s default page
• A completely different website
• A connection error
• A parked domain page

How to Find the Correct IP Address

Your hosting provider normally displays the server IP somewhere inside your hosting dashboard.

Depending on the hosting company, it may be listed as:

• Shared IP address
• Server IP
• Account IP
• IPv4 address
• Dedicated IP

Compare that IP address with your domain’s A record.

If they do not match, the domain may be pointing to the wrong server.

Be Careful With Existing DNS Records

Do not automatically delete every existing record.

Some records may be required for:

• Email
• Verification services
• Subdomains
• Third-party applications
• Marketing platforms
• Payment services

The goal is to correct the website-related records without breaking other services.

3. Check the www Version of Your Domain

Your website has two common versions:

example.com

and

www.example.com

Both should normally lead visitors to the same website.

Problems can occur when only one version is configured correctly.

For example:

example.com → works

www.example.com → error

Or the opposite.

The www version is usually handled through a CNAME record or another DNS configuration depending on the hosting setup.

You should also check which version WordPress is configured to use.

Go to:

WordPress Dashboard → Settings → General

Check:

WordPress Address (URL)

and

Site Address (URL)

These should normally use the correct final domain and protocol.

For example:

https://example.com

Do not change these values randomly if you are already dealing with an active redirect or SSL problem.

4. Check for an Incorrect AAAA Record

One DNS problem that is often overlooked is an incorrect AAAA record.

An A record is used for IPv4.

An AAAA record is used for IPv6.

Your website can therefore have a correct A record but an incorrect AAAA record.

This can create a confusing situation where some visitors can access the website while others experience connection problems.

For example, you might have:

A: Correct IPv4 address

AAAA: Old or incorrect IPv6 address

Depending on the visitor’s network, the browser may attempt to connect using IPv6 and reach the wrong server.

If your hosting provider does not use IPv6, an outdated AAAA record may need to be removed.

However, do not delete an AAAA record simply because you do not recognize it. Confirm whether your hosting environment actually uses IPv6 first.

5. Remove Old DNS Records After a Hosting Migration

Moving WordPress to a new hosting provider is one of the most common situations where DNS problems appear.

For example:

Old host: Server A
New host: Server B

You move the WordPress files and database to Server B, but the domain still points to Server A.

The new website may be perfectly installed, but visitors continue reaching the old server.

If you are moving a WordPress website, DNS is only one part of the process. You also need to make sure the WordPress files, database, domain configuration, SSL certificate, and redirects are all working correctly.

If you are planning a migration, see our guide on moving WordPress to a new host before changing your DNS.

6. Check Your WordPress URL Settings

DNS determines where the domain points.

WordPress determines which URL the website considers to be its official address.

These two configurations need to agree.

For example, DNS may point:

example.com

to your server correctly.

But WordPress could still be configured as:

http://example.com

instead of:

https://example.com

or:

https://www.example.com

This mismatch can cause redirect and SSL problems.

Check:

Settings → General

and verify both:

WordPress Address (URL)

and

Site Address (URL)

Use the exact domain and protocol that your website is supposed to use.

7. Check SSL After Changing DNS

A DNS change and an SSL change are often connected.

Suppose you move your website from:

Old Host → New Host

and update the DNS records.

The domain may begin reaching the new server, but the new server may not yet have a valid SSL certificate.

The result could be:

• SSL certificate errors
• HTTPS warnings
• Redirect loops
• Mixed HTTP/HTTPS behavior
• Browser security warnings

After changing DNS, verify that the new hosting account has a valid SSL certificate for both the main domain and the required www version.

If your WordPress website has broader SSL or HTTPS configuration problems, troubleshoot those separately rather than repeatedly changing DNS records.

8. Check for HTTPS Redirect Loops

One of the most common symptoms after changing DNS or enabling Cloudflare is:

ERR_TOO_MANY_REDIRECTS

A typical redirect chain might look like:

HTTP → HTTPS → HTTP → HTTPS

The browser keeps being redirected and eventually gives up.

This can happen because multiple systems are trying to control HTTPS:

• WordPress
• Your hosting server
• Cloudflare
• An SSL plugin
• .htaccess
• Another redirect rule

Check Your SSL Mode

If Cloudflare is being used, check the SSL/TLS configuration.

A mismatch between Cloudflare and the origin server can create unnecessary redirects.

For example, Cloudflare may connect to the server using HTTP while WordPress or the server expects HTTPS.

The solution is not always to disable SSL plugins or rewrite .htaccess rules.

First determine which service is responsible for the redirect.

9. Check Cloudflare DNS Configuration

Cloudflare can be extremely useful for WordPress websites, but it adds another layer between the visitor and your hosting server.

The connection becomes:

Visitor → Cloudflare → DNS → Hosting server → WordPress

This means you need to check both Cloudflare and your hosting configuration.

If the DNS record inside Cloudflare points to the wrong IP address, changing DNS at your registrar will not solve the problem if the registrar is only delegating nameservers to Cloudflare.

Check:

• A records
• AAAA records
• CNAME records
• Proxy status
• SSL/TLS settings
• Redirect rules
• Page rules if applicable
• Cache configuration

Do not change several Cloudflare settings simultaneously. Make one change, test the website, and then continue.

10. Clear Local DNS and Browser Cache

Sometimes the DNS configuration is already correct, but your computer is still using an older DNS response.

This can happen after:

• Changing DNS records
• Moving hosting
• Changing nameservers
• Changing the domain’s IP address

Try the website in a private/incognito browser window.

You can also test it from:

• A different browser
• A phone using mobile data
• Another computer
• A different network

If the website works on mobile data but not on your computer, the problem may be local DNS caching rather than the website itself.

Your operating system and DNS resolver may need time to update the stored result.

11. Understand DNS Propagation

DNS changes are not always visible everywhere immediately.

After changing a DNS record or nameservers, different networks may temporarily return different results.

This is commonly referred to as DNS propagation.

During this period:

• Some visitors may reach the old server
• Others may reach the new server
• Your computer may show one result
• A visitor in another country may see another

This is particularly common after moving WordPress to a new host.

Avoid repeatedly changing the DNS configuration because one device still shows the old website.

First determine whether the change is actually propagating.

12. Check Whether the Domain Has Expired

This sounds obvious, but it is worth checking.

If the domain registration has expired, the website can stop working regardless of whether your WordPress installation and hosting account are perfectly configured.

Check:

• Domain expiration date
• Registrar status
• Nameservers
• Domain lock status
• DNS configuration

If the domain recently expired and was renewed, DNS or nameserver behavior may also temporarily change.

13. Check Domain Forwarding

Some registrars offer domain forwarding.

For example:

example.com → anotherdomain.com

This is different from pointing the domain directly to your WordPress hosting server.

If forwarding is configured when you actually need the domain to resolve directly to your hosting account, it can create unexpected redirects or prevent your intended DNS setup from working properly.

If your WordPress site is supposed to be hosted directly on the domain, verify that unnecessary forwarding is disabled.

14. Check DNS Records for Email

Changing DNS can affect more than your website.

Your email may depend on records such as:

• MX
• SPF
• DKIM
• DMARC

This is especially important when changing nameservers.

You may successfully point the website to a new server and accidentally break email delivery by replacing or removing existing mail-related records.

Before changing nameservers, document the existing DNS records.

If your WordPress website also sends transactional email, make sure your SMTP configuration remains functional after the DNS changes.

This is particularly important for:

• Contact forms
• WooCommerce orders
• Password reset emails
• Customer notifications
• Lead forms

15. Check DNSSEC Configuration

DNSSEC adds another layer of validation to the DNS system.

When configured correctly, it helps protect DNS responses from certain types of manipulation.

However, incorrect DNSSEC configuration can make a domain unreachable.

This can happen after:

• Changing DNS providers
• Changing nameservers
• Moving a domain
• Removing a DNS provider
• Restoring an old DNS configuration

If the domain suddenly stopped resolving after a nameserver change, check whether DNSSEC is configured correctly at the registrar and DNS provider.

Do not change DNSSEC settings blindly. If you are not sure how the domain was configured, check the registrar’s documentation or support first.

16. Check for Old Redirects and .htaccess Rules

DNS is not responsible for every domain-related problem.

Sometimes the DNS is correct, but the server is redirecting visitors incorrectly.

This can happen because of:

• .htaccess rules
• Redirect plugins
• SSL plugins
• Server-level redirects
• Old migration rules
• WordPress URL changes

For example, a website may correctly resolve to the new server but immediately redirect visitors back to the old domain.

That is no longer primarily a DNS problem.

It is a website or server configuration problem.

If your website returns a 500 Internal Server Error after making configuration changes, investigate the server and WordPress environment separately rather than continuing to change DNS records.

17. Check for Redirect and Caching Plugins

WordPress plugins can also interfere with domain changes.

Common examples include plugins that handle:

• Redirects
• SSL
• Caching
• Security
• URL replacement
• CDN integration

If the domain was recently changed or the website was migrated, temporarily reviewing these plugins can help identify whether WordPress is generating unexpected redirects.

Do not disable every plugin at once if the website is live.

Instead, identify plugins related to:

• redirects
• SSL
• caching
• CDN
• security

and investigate those first.

18. What Does ERR_NAME_NOT_RESOLVED Mean?

The error:

ERR_NAME_NOT_RESOLVED

usually indicates that the browser cannot resolve the domain name to an IP address.

Possible causes include:

• Missing DNS records
• Incorrect nameservers
• Domain expiration
• DNS provider problems
• Incorrect domain configuration
• DNS propagation
• Local DNS cache

Start by checking whether the domain has the correct active nameservers.

Then verify the A and AAAA records.

If the DNS configuration is correct but the error appears only on one device, test the domain from another network.

19. What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?

NXDOMAIN generally means that the DNS system is reporting that the requested domain does not exist.

This can happen when:

• The domain is not properly delegated
• Nameservers are incorrect
• DNS records are missing
• The domain has expired
• DNSSEC is incorrectly configured

If the domain recently changed registrars or nameservers, start there.

Do not immediately modify WordPress because WordPress may not even be receiving the request.

20. What If the Wrong Website Loads?

Sometimes the domain loads a website, but it is not your website.

This is an important clue.

It often means the domain is reaching a valid server, but that server is configured for another website.

Possible causes include:

• Wrong A record
• Old hosting IP
• Incorrect virtual host configuration
• Shared hosting configuration problem
• Domain added incorrectly to the hosting account
• Old server still receiving traffic

Check the DNS IP first.

If the IP is correct, contact the hosting provider and ask them to verify that the domain is correctly assigned to the intended hosting account.

21. What If the Website Works on One Device but Not Another?

This situation usually means you should investigate DNS caching or propagation before changing WordPress.

Test the domain using:

• Mobile data
• A different Wi-Fi connection
• Incognito mode
• Another browser
• Another computer

If the website works everywhere except one network, the issue is probably not the WordPress installation itself.

The problem may involve:

• Local DNS cache
• ISP DNS cache
• Router DNS cache
• Corporate network filtering
• Security software

This simple test can save a lot of unnecessary troubleshooting.

A Practical WordPress DNS Troubleshooting Process

When a WordPress domain stops working, use this order instead of changing random settings.

Step 1: Check the domain

Make sure the domain is registered and active.

Step 2: Check nameservers

Confirm which DNS provider is actually controlling the domain.

Step 3: Check the A record

Make sure the domain points to the correct hosting server.

Step 4: Check www

Make sure the www version resolves correctly.

Step 5: Check AAAA

Look for an incorrect IPv6 record.

Step 6: Check the hosting account

Make sure the domain is actually configured on the intended server.

Step 7: Check SSL

Verify that the new server has a valid certificate.

Step 8: Check WordPress URLs

Confirm that the WordPress and Site URLs use the correct domain and HTTPS configuration.

Step 9: Check redirects

Look at .htaccess, redirect plugins, Cloudflare rules, and server-level redirects.

Step 10: Test from another network

This helps determine whether the issue is local caching or a real DNS problem.

Following this sequence prevents you from changing several unrelated settings and making the problem harder to diagnose.

How to Prevent WordPress DNS Problems in the Future

DNS problems are much easier to prevent when you document your configuration before making major changes.

Before moving hosting or changing nameservers, record:

• Current nameservers
• A records
• AAAA records
• CNAME records
• MX records
• SPF records
• DKIM records
• DMARC records
• Current hosting IP
• Current WordPress URL
• SSL configuration

This gives you a reference point if something stops working.

It is also a good idea to keep your domain registration, DNS provider, and hosting information organized so you know exactly where each part of the website is managed.

When migrating WordPress, do not treat DNS as an isolated task. The migration also involves the hosting server, WordPress configuration, SSL, redirects, email, caching, and sometimes CDN settings.

Final Thoughts

WordPress DNS and domain configuration problems can look complicated because several different systems are involved.

The important thing is to troubleshoot them in the correct order.

Start with the domain and nameservers. Then check the A and AAAA records, verify the hosting server, check the www configuration, and confirm that WordPress and SSL are using the correct domain.

If the domain resolves but the website redirects incorrectly, move your investigation toward WordPress, .htaccess, Cloudflare, SSL, or redirect plugins.

And if the website works on one network but not another, investigate DNS caching and propagation before changing the website itself.

Once you understand the relationship between domain → DNS → hosting → SSL → WordPress, most domain configuration problems become much easier to identify.

If you want to go beyond individual troubleshooting fixes and learn how WordPress hosting, performance, security, SEO, WooCommerce, and website optimization work together, the WP Flow Mastery WordPress eBook covers these areas in one practical 160+ page guide.

Written by Nemanja Stosic

WordPress Developer & Website Optimization Specialist

Nemanja has worked on more than 200 websites and focuses on WordPress development, performance optimization, SEO, security, WooCommerce, and practical website improvements.