Why did my website or email stop working after I changed DNS records, and how do I fix it without breaking everything?

If your website went offline or your email stopped arriving right after a DNS change, the problem is usually not “the internet is broken” — it’s that one of the records telling browsers and mail servers where to go now points somewhere else, or nowhere at all.

The good news: this is usually fixable without rebuilding your site or email from scratch. The safest path is to identify which record changed, restore only the affected entries, and then let DNS propagation finish before you make another move.

What DNS actually does

DNS is the internet’s address book.

When someone types your domain into a browser, DNS tells that browser where your website lives. When someone sends you an email, DNS tells the sending server where to deliver it.

That means one small edit can affect:

your website
your email inbox
subdomains like www or mail
SSL/certificate setup
verification for services like email platforms or third-party tools

The most common reasons things break after a DNS change

1. The website record now points to the wrong place

For most sites, the key records are:

A record — points your domain to an IP address
AAAA record — the IPv6 version of an A record
CNAME record — points one name to another name, often www to your root domain

If the A or CNAME record was changed, deleted, or copied incorrectly, your site may load the wrong page or stop resolving entirely.

2. Email routing was changed

Email usually depends on:

MX records — tell the world where to deliver mail
TXT records — often used for SPF, DKIM, and domain verification

If the MX record is wrong, email can bounce or disappear. If a TXT record was removed, some providers may stop trusting your domain or mark messages as suspicious.

3. The change is still propagating

DNS updates do not reach every server instantly.

During propagation, some people may still see the old destination while others see the new one. That can make it look like your site or email is “randomly” broken when the records are actually still updating across the network.

4. You changed nameservers instead of just records

This is a common gotcha.

If you changed DNS records, you edited the zone.
If you changed nameservers, you moved DNS hosting to a different system.

When nameservers change, the old DNS records may no longer control your domain at all. In that case, fixing the old zone won’t help until the correct provider has the right records in place.

5. A supporting record was altered

Some records do not point traffic directly, but they still matter:

SRV — used by some apps and services for connection details
CAA — controls which certificate authorities can issue SSL certificates for your domain
DNSSEC — adds protection, but if configured incorrectly it can prevent resolution

If one of these was changed during a broader cleanup, you may see side effects even if the website and MX records look right.

How to fix it without breaking everything else

Step 1: Stop making more changes

The fastest way to turn a small issue into a bigger one is to keep editing while you’re unsure.

Pause, then gather what changed:

screenshots of the current DNS zone
the original values, if you have them
any recent setup emails from your hosting or email provider
the time the issue started

Step 2: Identify what is broken

Test the website and email separately.

Ask:

Does the root domain fail, or only www?
Does the site load, but email is down?
Are incoming messages bouncing, or are they just landing in spam?
Did both break at the same time?

That tells you which records to inspect first.

Step 3: Restore the website records first

If the site is down, start with the web routing records:

confirm the A record points to the correct hosting IP
confirm the CNAME for www points to the right host or root domain
check whether an AAAA record was added accidentally and is sending some visitors to the wrong place

If you’re using a website builder or hosting plan, make sure the domain matches the destination required by that service.

Step 4: Restore email routing next

If email stopped working, check the mail records:

confirm the MX record matches your email provider
restore any required TXT records for email authentication or verification
make sure records for the right subdomain are in place if your provider uses one

If you use Network Solutions Professional Email and your domain is already with Network Solutions, setup is simpler because you can usually select the domain from a list during setup. If your domain is elsewhere, you’ll need to copy the provided DNS values into your current domain provider’s DNS settings.

Step 5: Wait for propagation before changing anything else

Once you restore the correct records, give DNS time to settle.

During this period:

some users may still see the old site
some mail may still route using cached information
tests from different devices or networks may show different results

That does not always mean the fix failed. It often means the update is still moving through the system.

Step 6: Verify SSL and service settings after DNS is corrected

Once traffic reaches the right server again, check the next layer:

does the SSL certificate match the domain?
does the site load over HTTPS without warnings?
are email apps connecting with the right settings?

If the domain now resolves but the browser shows a security warning, the DNS may be fixed while the certificate still needs attention.

A safe recovery checklist

Use this order when you want the least risk:

Back up current DNS values
Fix one record type at a time
Start with A/CNAME for the website
Then restore MX and TXT for email
Leave SRV, CAA, and DNSSEC alone unless you know they were changed
Wait for propagation
Test from multiple devices or networks
Only then make the next adjustment

How to prevent this next time

A little discipline saves a lot of downtime.

Keep a copy of your working DNS records before editing
Change only what you need, not the whole zone
Make one change, test it, then move to the next
Document which service each record supports
Avoid editing during busy hours if your site or inbox is mission-critical
Use one account and one support path so the domain, hosting, email, and SSL stay under one roof

When to contact support

Reach out if:

you do not know which record changed
both website and email are down
you changed nameservers and are unsure where DNS is hosted
DNSSEC is enabled and resolution is failing
you need help restoring mail settings, SSL, or a website launch after a DNS update

With Network Solutions, you can use the Help Center article on managing DNS and advanced DNS records for the step-by-step record list, or contact support through chat or phone for live help.

The short version

Your website or email likely stopped working because DNS now points traffic to the wrong destination, or the new values have not finished propagating yet.

The safest fix is simple:

restore the correct website records
restore the correct mail records
wait for propagation
test before making another change

If you want, I can also turn this into a shorter troubleshooting checklist or a step-by-step guide specifically for website down, email down, or both down after DNS change.