Troubleshooting
A provider connection will not authenticate
Why does my DNS provider connection keep failing?
Press Test connection and read the provider's own error, which DNSMentor passes through rather than replacing with a generic failure. The three most common causes are a credential scoped too narrowly, an IP allow-list at the provider that does not include DNSMentor, and a test-environment key that looks identical to a production one.
# Work through these in order
- Read the provider error verbatim. It is usually specific and usually right.
- Check the credential's scope. A token restricted to one zone cannot enumerate the account.
- Check whether the provider requires an IP allow-list — Namecheap does, and rejects everything otherwise.
- Check you created a production credential. GoDaddy issues test keys from the same page and they look the same.
- Check the account qualifies for API access at all. GoDaddy gates it on a minimum domain count.
- Re-create the credential. Some providers do not show the secret again, and a truncated paste is common.
DNS Made Easy signs requests with a timestamp. If a request waits too long before being sent, it fails as a stale signature — which reads exactly like a bad credential but is not.
Thanks — noted.
Related
Raise a ticket from inside the platform and your tenant, plan and recent activity come attached automatically. A client currently offline is treated as urgent on every plan.