Common symptoms
Your site was working temporarily, but suddenly stopped displaying
You see a "Your connection is not private" message
The Publish panel shows "Connection could not be verified"
These symptoms are often caused by issues with your DNS record settings.
This article explains how to check your DNS record settings and how to resolve any issues.
Point: For detailed steps on publishing your site, see Publishing your site with a custom domain.
Note: If you're using Cloudflare, please disable DNS Proxy mode. If it's left enabled, your certificate may fail to be issued or renewed correctly.
How to check your DNS record settings
Use the following steps to check that your domain's A record, AAAA record, CNAME record, and CAA record are all set up correctly.
Go to Google's checking tool, Google Admin Toolbox Dig.
In the "Name" field, enter your custom domain (for example, Studio.design), then click "ANY."
Check the results for the following record types. Note that any record types not supported by this tool won't appear in the results.
(1) A record
(2) AAAA record
(3) CNAME record
(4) CAA record
(1) Checking your A record
Your setup is correct if only one of the following addresses is displayed:
Studio.Design's IP address: 34.111.141.225
Studio.Design's former IP address: 35.194.122.208
If a different address appears, you'll need to check and update your DNS record settings. See the solutions below based on your specific situation:
Note: If "35.194.122.208" is displayed, this is Studio.Design's former IP address. If you disconnect while using this former IP address—whether mid-setup or after publishing—you won't be able to reconnect using the same IP address. You'll need to reconnect using the new IP address (34.111.141.225) instead.
For more details, see If your custom domain is connected to Studio.Design's former IP address (35.194.122.208).
1. An address other than "34.111.141.225" or "35.194.122.208" appears
This usually means the A record update either hasn't been completed yet or hasn't been made at all.
Studio.Design can't check the status of your DNS record changes. Please contact your name server (DNS server) provider for assistance.
2. Multiple addresses appear
Make sure only Studio.Design's IP address remains in your A record.
In your DNS service, delete any A records other than Studio.Design's IP address.
Wait for the changes to take effect. This can take up to 48 hours.
Note: If the address (A record) you're about to delete is being used by a third-party email service, deleting it will disable that email service.
Typically, A records are used for websites, while MX records are used for email accounts. If your email service supports MX records, you can display your website through Studio.Design while continuing to use your email service with the same domain through a different provider.
For details, please contact the support team for your name server (DNS server) provider.
3. "Record not found!" appears
After creating or updating a DNS record, it can take anywhere from 2 to 48 hours for the change to fully take effect everywhere. If you see "Record not found!," this could mean one of the following:
The change hasn't fully propagated yet: Wait up to 48 hours for it to take effect.
There's an issue with your DNS settings: Contact your DNS service for help.
How to check propagation status
If you see "Record not found!," you can check whether your DNS record has propagated using the steps below.
Go to a DNS checking tool.
Enter the domain you want to check, select the "A" record type, and click "Search."
Check the icons shown in the results.
Green checkmark: The change has propagated.
Red X mark: There's an issue with your DNS record settings, or the change hasn't propagated yet. Wait a while, then check again using the tool.
If the issue persists over time
If the issue still isn't resolved after waiting, the problem may be with your DNS server for one of the reasons below. Since Studio.Design can't see these details, please contact the support team for your DNS server provider.
The record information was entered in the wrong location
Your domain registration or DNS server contract with your domain provider has expired
A payment to your name server provider has failed
Your domain registrant information hasn't been verified
Your DNS server settings are incorrect
(2) Checking your AAAA record
For the domain you want to use with your Studio.Design site, it's normal for the AAAA record to be empty. Since Studio.Design doesn't support AAAA records (IPv6 addresses), having one set up will cause your TLS certificate issuance to fail.
If any IP address appears in the AAAA record, delete it in your DNS service and wait for the change to take effect.
(3) Checking your CNAME record
For the domain you want to use with your Studio.Design site, it's normal for the CNAME record to be empty.
If any value appears in the CNAME record, delete it in your DNS service and wait for the change to take effect.
Studio.Design doesn't support CNAME (Canonical Name) records. Setting one up to redirect a subdomain like "www" won't work.
To make your site accessible with or without the "www" prefix, set up a www redirect.
(4) Checking your CAA record
In most cases, you don't need to set up a CAA record. However, if you're connecting a subdomain and the root domain already has a CAA record specified, you'll need to add one for the subdomain too.
In this case, add the following CAA records to your subdomain's DNS settings and wait for them to take effect. Once they have, try reconnecting your custom domain.
pki.goog
*If your A record points to Studio.Design's former IP address (35.194.122.208), only specify letsencrypt.org.
If these steps don't resolve your issue, please log in to Studio.Design and click the [?] icon in the bottom left of the editor to contact support. Sharing details about your situation and what you've already checked will help us assist you more quickly.
Privacy error Your connection is not private