Hey yall!
As those of you with Custom Domains configured in Retool may have seen, we sent out an email to let orgs with Custom Domains know that we will be making some infrastructure improvements that require you to update the DNS before September 7, 2026.
We’ve received a couple of reports of orgs whose Custom Domains CNAME were pointing to the wrong target.
When running the dig command to check (as outlined in our docs, they had the following output:
$dig <custom-domain> CNAME +noall +answer
; <<>> DiG 9.10.6 <<>> <custom-domain> CNAME +noall +answer
;; global options: +cmd
<custom-domain>. 300 IN CNAME xn--custom-domain-gk6gha.xn--retool-gf0c.com.
DNS was resolving to the incorrect CNAME record
This is due to copy and pasting from the email, as there were zero-width space characters in the HTML. If your org is unable to connect via Custom Domain after updating your DNS, be sure your CNAME record maps your Retool domain to Retool’s alias for custom domains:
custom-domain.retool.com
Sorry for any disruptions!