Site publishing steps and common issues
With Studio.Design, you can connect your own custom domain to a website you've built and publish it. Here are the steps for publishing your site:
Register your domain in the Publish panel
Confirm the domain connection
Publish the site
If "2. Configure DNS records" isn't set up correctly, your site may not publish properly.
Examples of publishing issues:
Your site was visible for a while, then suddenly stops displaying
A message saying "Your connection is not private" appears
Studio.Design's Publish panel shows "Connection could not be verified"
In this article, we'll show you how to check whether your DNS records are set up correctly and how to fix any issues.
Note: If you're using Cloudflare
If you use Cloudflare, please disable DNS Proxy mode. When it's enabled, certificate issuance or renewal may not work properly.
How to check your DNS record settings
Use the steps below to confirm that the A, AAAA, CNAME, and CAA records for the domain you want to use are configured correctly.
Open Google's diagnostic tool (Google Admin Toolbox Dig).
Enter your custom domain (for example, Studio.design) in the "Name" field, then click "ANY".
Review the following records in the results:
(1) A record
(2) AAAA record
(3) CNAME record
(4) CAA record
*Records that the tool can't check won't appear in the results.
(1) Check the A record
It's working correctly if only one of the following is displayed:
Studio.Design's IP address: "34.111.141.225"
Studio.Design's legacy IP address: "35.194.122.208"
If anything else appears (see below), you'll need to review and update your DNS records. See the sections below for how to resolve each situation.
Note: If "35.194.122.208" is shown
"35.194.122.208" is Studio.Design's legacy IP address. If you're connected via this legacy IP and you disconnect the domain during setup or after publishing, you won't be able to reconnect using the same IP (35.194.122.208) — you'll need to reconnect using the new IP address (34.111.141.225).
1. An address other than "34.111.141.225" or "35.194.122.208" is shown
In this case, the A record change may not have been completed, or the update may not have been made.
We're unable to check details such as the status of your DNS record changes on our end. Please contact your name server (DNS server) provider.
2. Multiple addresses are shown
Leave only Studio.Design's IP address in the A record.
In your DNS service, delete any A records that aren't Studio.Design's IP address.
Wait for the changes to take effect. This typically takes around 48 hours.
Note: If you use a third-party email service
If the address (A record) you're deleting is being used by another email service, deleting it will stop that email service from working. Please be careful.
In general, A records are used for websites and MX records are used for email accounts. As long as your email service supports MX records, you can display your website on Studio.Design while using a third-party email service on the same domain.
For details, please contact your name server (DNS server) provider's support team.
3. "Record not found!" is shown
When you create or change a DNS record, it typically takes 2 to 48 hours to propagate worldwide. If you see "Record not found!", one of the following may apply:
Propagation isn't complete yet: Please wait up to 48 hours.
There's an issue with your DNS settings: Please contact your DNS service.
How to check propagation status
If "Record not found!" appears, you can check the propagation status of your DNS record as follows:
Open the DNS checker tool.
Enter the domain you want to check, select the "A" record, and click "Search".
Check the icons displayed in the results.
Green checkmark: Propagated
Red X mark: There may be an issue with your DNS record settings, or propagation isn't complete. Wait a while and check again with the checker tool.
If the issue isn't resolved after waiting
If the issue doesn't resolve over time, the cause is likely on the DNS server side. We're unable to check the details on our end, so please contact your DNS server provider's support team. Possible causes include:
The record information is set up in the wrong location
Your domain registration or DNS server contract with the domain provider has expired
Payment to your name server has failed
Domain registrant information hasn't been verified
DNS server settings are incorrect
(2) Check the AAAA record
For the domain you want to use on a Studio.Design site, the AAAA record should be empty. Studio.Design doesn't support AAAA records (IPv6 addresses), so if one is set, TLS certificate issuance will fail.
If an IP address appears in the AAAA record, delete it from your DNS service and wait for the change to propagate.
(3) Check the CNAME record
For the domain you want to use on a Studio.Design site, the CNAME record should be empty.
If an IP address appears in the CNAME record, delete it from your DNS service and wait for the change to propagate.
Studio.Design doesn't support CNAME (Canonical Name) records. Setting one to redirect subdomains like "www" won't work. If you use the custom proxy feature, your website can be displayed at both the www and non-www URLs. For details on how to set up a custom proxy, see Set up a custom proxy.
(4) Check the CAA record
You generally don't need to set a CAA record. However, if you're connecting a subdomain and a CAA record is already set on the root domain, you'll need to configure one.
In this case, add the following CAA records to your subdomain's DNS settings, wait for the changes to propagate, then try reconnecting your custom domain.
pki.goog
* If you're using Studio.Design's legacy IP address (35.194.122.208) in your A record, only set letsencrypt.org.
If the steps in this article don't resolve the issue, sign in to Studio.Design and click the [?] in the lower-left corner of the editor to contact support. Including details about your situation and what you've already checked will help us assist you more quickly.
Privacy error Your connection is not private