Home/HighLevel/Troubleshooting/DNS not verifying
Troubleshooting · Domains
Fix: GoHighLevel DNS records not verifying. Host names cause most of it.
DNS verification usually fails on small details: a host name with the domain added twice, a missing dot, an old conflicting record or a record added at the wrong DNS provider.
The short answer
DNS records fail to verify in GoHighLevel when the host name is wrong (often the domain added twice by the provider), a value has a typo, an old record conflicts, the record is at the wrong DNS host, or propagation is still in progress.
Michael is a sponsored HighLevel affiliate. Links to HighLevel use his partner link at no extra cost to you. HighLevel prices and product facts on this page come from HighLevel's own pricing page and help center, checked on the date above.
Causes
Why are DNS records not verifying in HighLevel?
Most cases come down to the five causes in this table. Check each one before you change anything.
| Cause | How to check |
|---|---|
| Domain added twice | Host shows mail.yourdomain.com.yourdomain.com |
| Typo in value | Compare character by character |
| Conflicting record | Another record on the same host |
| Wrong DNS host | Nameserver location |
| Propagation | Time since change |
Diagnose
How do you confirm why the DNS records fail before you change them again?
Look at what the world sees, not what you typed. Use any public DNS lookup tool to query the exact host name HighLevel asked for. Three results are possible. The record comes back with the right value, which means it is only a matter of time. It comes back with a different value, which means a typo or a conflicting record. Or nothing comes back, which usually means the host name is wrong or the record was added at the wrong DNS host.
When nothing comes back, try the lookup with your domain added a second time on the end, such as mail.yourdomain.com.yourdomain.com. If that returns your record, the provider added the domain automatically and you typed it as well. Enter only the subdomain part as the host.
Then confirm where the DNS is hosted by checking the nameservers, and open the record list there. In HighLevel, the records to match are under Settings, Email Services, Dedicated Domain and IP for a sending domain, as shown in set up SPF, DKIM and DMARC. For a website or funnel domain they are under Sites, Settings, Domains, covered in fix a custom domain not connecting.
Fix
Fix it step by step.
- Compare each record with what HighLevel shows.
- If your provider adds the domain automatically, enter only the subdomain part as the host.
- Remove conflicting records on the same host.
- Confirm you edited the DNS host the nameservers point to.
- Wait and verify again.
Still stuck
When to contact support.
If none of these fix it, open Help and Support from the question mark at the top right of your agency view, then start a chat (AI Support Chat or Agent Chat), join a Zoom call or open a ticket. Have your Agency Relationship Number and the Location ID of the subaccount ready, add screenshots of the problem, and turn on Support Access so the team can look inside the account. Only Agency Admins and Agency Users can reach HighLevel support; subaccount users go through their agency.
- Screenshot records before and after changes
If the public lookup shows the right values and HighLevel still will not verify, send support the domain, the DNS provider, screenshots of the records on both sides and the lookup result with the time you ran it.
For prevention, screenshot records before and after every change and edit one record at a time. Once records verify, check that mail actually passes: SPF, DKIM or DMARC failing covers alignment, and warming up the sending domain comes next.
Not on the platform yet? The GoHighLevel 30 day trial through Michael's link lets you set this up and test it before the first invoice. Still weighing the monthly cost? Read is HighLevel worth it.

Most DNS failures are one extra copy of the domain in the host field.
Questions
Common questions.
Why is my DNS records not verifying?
DNS records fail to verify when the host name is wrong (often the domain added twice by the provider), a value has a typo, an old record conflicts, the record is at the wrong DNS host, or propagation is still in progress.
How do I prevent it?
Screenshot records before and after every change and edit one record at a time.
When should I contact HighLevel support?
Contact support once you have checked every cause on this page and it still fails, or when the fix sits on HighLevel's side. If the public lookup shows the right values and HighLevel still will not verify, send support the domain, the DNS provider, screenshots of the records on both sides and the lookup result with the time you ran it.
How long do DNS records take to verify in HighLevel?
It depends on the DNS provider. Changes can take up to 24 hours to propagate. If a public DNS lookup already shows the right value, wait and verify again.
What do I enter in the host field for a DNS record?
Enter the host exactly as HighLevel shows it, unless your provider adds the domain automatically. In that case enter only the subdomain part, such as mail, so the domain does not appear twice.
Can I add the records where I bought the domain?
Only if that company also hosts the DNS. Records must be added at the DNS host the nameservers point to. Records added anywhere else have no effect.
Next step
See it in your own account. Thirty days, every feature.
Start a 30 day trial through Michael's link, build the first system and test it before the first invoice. Usage fees for phone, SMS, email and AI can apply during the trial.
HighLevel has three plans at a flat monthly price, each with unlimited users and contacts. See what each one includes and what it costs.
Compare the PlansStarter, Unlimited and Founder