FR Lire en français

Domain DNS errors

TXT not found, CNAME not found, CNAME points elsewhere, or a root domain that does not resolve: the fix for each.

For:
  • Integrators
  • Developers

In short: most DNS errors come from a name typed twice, an old record left in place, or changes that are not visible yet. Fix the record, wait 15 minutes, then click Verify.

“We could not find the TXT record yet”

  • Name typed twice: many providers add your domain to the name for you. Enter _sofast-verify.www, not _sofast-verify.www.mystudio.com.
  • Value incomplete: copy the full value from your dashboard, with no space before or after.
  • Not visible yet: new records can take a few hours to appear everywhere.

“We could not find the CNAME record yet”

Check that the CNAME is on the right name (www for www.mystudio.com) and that you saved it. Then wait and click Verify again.

“The CNAME record points somewhere else”

An old record is still in place, often from a previous host or a parking page. Delete any other A, AAAA or CNAME record on that name, then set the CNAME value to domains.sofast.website.

“This bare domain does not point to SoFast yet”

You entered mystudio.com without www, and your provider does not support CNAME flattening, ALIAS or ANAME. Connect www.mystudio.com instead and redirect the root domain. See Root domain vs www.

Check from your terminal (optional)

dig +short TXT _sofast-verify.www.mystudio.com
dig +short CNAME www.mystudio.com

The second command should return domains.sofast.website. Provider steps: GoDaddy, Namecheap, Cloudflare, OVHcloud, Squarespace.

Still stuck? Contact us