Why your custom domain isn't connecting, and how to fix it
To publish a site built with Studio.Design using a custom domain, follow these steps:
Register your domain in the Publish panel
Configure your DNS records
Verify the domain connection
Issue a TLS certificate
Publish your site
In step 3, "Verify the domain connection," Studio.Design checks whether your domain is pointing to our servers correctly. If the connection can't be verified for any reason, an error will appear in the Publish panel. This article explains the types of errors you might see, what causes them, and how to fix them.
Types of errors
One of the following alerts will appear in orange in the Publish panel. In most cases, these errors are caused by your DNS record settings, so you'll need to review them.
Keep in mind that DNS setting changes generally take 2 to 48 hours to take effect. If you've only just made changes, your domain connection may not be verifiable yet. While you're waiting for the changes to apply, there's nothing you can do from the Studio.Design side to speed things up.
You can check the status of your DNS changes using external tools like Google Admin Toolbox Dig or DNSChecker.org. For details on how to use these tools, see the article below.
(1) We can't verify where your domain is pointing
This means your A record isn't pointing to Studio.Design correctly. The A record may not have been entered, or a CNAME record may have been set up instead.
Use an external tool like Google Admin Toolbox Dig to check your record settings. For details on how to use these tools, see the article below.
Common causes
If you've set up the A record but still see an error, here are some other possible causes. For details on any of these, please reach out to your DNS provider's support team.
You're editing the wrong DNS server
The DNS server you added the A record to may not be the one your domain is actually using. You can check which DNS server is in use with a tool like Whois.DNSSEC isn't set up correctly
This can happen when you transfer your DNS server. If DNSSEC was left enabled on the previous DNS server during the transfer, your DNS records may not be visible externally.
(2) Your domain is pointing to a different server
This means a record other than Studio.Design's has been set in your DNS settings.
In your DNS settings, delete the non-Studio.Design record shown in the Publish panel, set the correct Studio.Design A record, and then try verifying the connection again.
Common causes
If you've set up the A record but still see an error, here are some other possible causes. For details, please reach out to your DNS provider's support team.
The name server on Onamae.com is still set to the default
If you're using Onamae.com to manage your domain, you have several name server options. However, if the name server is still set to the default DNS (dns1.onamae.com / dns2.onamae.com), any A records you set won't be visible externally. In this case, you'll need to switch to a different name server from the Onamae.com settings page.
(3) Your domain is pointing to multiple servers
This means two or more A records are set for your domain.
In your domain provider's DNS settings, delete any records without the Studio.Design mark shown in the Publish panel. Then try verifying the connection again.
If this article didn't answer your question, click the "?" in the bottom-right corner of the editor to contact our chat support team. It helps us respond faster if you include details about your situation and what you've already checked.