A business changing email providers
Moving from the host’s mailboxes to Google Workspace or Microsoft 365 needs new MX and TXT records. LayerAssist sets them and checks mail flows.
Check that your domain points where it should.
Your domain’s DNS records decide where visitors and emails go. One wrong record and your site or mail disappears. LayerAssist reads your records, explains them in plain words and fixes what’s wrong.
At a glance
- In chatIn chat, it reads your domain’s records — A, AAAA, CNAME, MX, NS and TXT — tells you who hosts your site and email, and finds what’s wrong.
- In chatWith access to where your DNS is managed, your hosting panel or your DNS provider’s account, it changes the records and checks the change took effect.
- AutomationAs your own automation, it can check on a schedule that your domain still points to your site and your mail records are still in place.
- Not available yetA built-in DNS monitor isn’t available yet.
Small DNS mistakes, big outages
DNS is the internet’s address book. When someone types your domain, DNS tells their browser which server holds your site; when someone emails you, it tells their mail server where to deliver. Nobody sees it — until it’s wrong.
A record changed during a hosting move, nameservers switched when a CDN was turned on, a mail record deleted by accident: the site disappears for some visitors, or email stops arriving, and it’s not obvious why.
Signs of a DNS problem
- “Server not found” or “DNS_PROBE_FINISHED_NXDOMAIN”
- The site shows an old version, or the old host’s page
- Email stopped arriving after a change to the website
- The site works with www but not without it, or the other way round
Common DNS mistakes
Records still pointing to the old host
After a move, the A record or CNAME often still points to the previous server.
Nameservers changed without the records
Switching nameservers to a new provider or CDN without copying every record drops whatever was left behind — often email.
Missing or wrong mail records
No MX record, or SPF, DKIM and DMARC records that don’t match your mail provider, means lost or filtered mail.
Conflicting or duplicate records
Two A records for the same name, or two SPF records, give visitors and mail servers different answers.
How LayerAssist checks and fixes DNS
It reads your domain the way the internet does, then explains what it sees.
Reads every important record
Nameservers, A and AAAA, CNAME, MX and TXT records, and what each one means for your site and email.
Finds who handles what
It works out which company runs your DNS, your website and your email, so you know where a change belongs.
Spots the mistakes
Records pointing to the wrong server, missing mail records, duplicates and conflicts.
Makes the change and verifies it
Where it has access to your DNS, it updates the records, then checks the new values are live.
Example: email gone after a website move
What it checks
- A record: points to the new hosting
- Nameservers: moved to the new host, but the mail records weren’t copied
- MX records: none, so mail has nowhere to go
- Mailboxes at your email provider: active
What it changes
Added the MX, SPF and DKIM records for your email provider to the new host’s DNS
What you get
- Your DNS explained in plain words
- Mistakes caught before they cost you visitors or email
- Changes made in the right place, then verified
- No need to learn record types yourself
Real situations
A site behind a CDN
After a CDN was switched on, some subdomains stopped working. LayerAssist compares the old and new zones and restores the missing records.
An agency taking over a domain
Nobody knows where the DNS is managed. LayerAssist reads the nameservers, identifies the provider and lists every record before anything changes.
How to check your domain’s DNS
Ask about your domain
In chat, write your domain and what’s wrong, or simply “Check my domain’s DNS”.
Connect where your DNS is managed
Reading records needs no login. To change them, connect your hosting panel or your DNS provider’s account.
Let it fix and verify
It updates the records and checks the new values are live.
Keep watching (optional)
Ask for a regular DNS check as your own automation, for example once a day.
Questions about DNS checks
The ones that matter for websites and email: nameservers (NS), A and AAAA, CNAME, MX and TXT records, including SPF, DKIM and DMARC.
Yes, where it can reach where your DNS is managed: your hosting panel or your DNS provider’s account. Afterwards it checks the change is live.
Often minutes, sometimes a few hours, depending on how long the old values may be cached. LayerAssist tells you what to expect and checks when the new values are live.
There’s no built-in DNS monitor yet. You can ask for a scheduled DNS check as your own automation; it runs as often as your plan allows.
Related guides
- In chatEmail deliveryChecks SPF, DKIM, DMARC and mailboxes, and fixes delivery.
- Built-in monitorSSL certificatesWarns before your certificate expires and fixes “Not secure”.
- Built-in monitorWebsite availabilityAlerts you when your site stops answering, then looks into why.
All monitoring guidesSee what each plan includesHow LayerAssist works
From $9 a month · 14 days to change your mind
Next time something breaks, you’ll know who to ask.
Add your website and ask your first question today. Not for you? Cancel within 14 days to get your first payment back, minus only the AI work you used.
Free for 7 days · No credit card needed · No technical knowledge needed.