Custom Domains
Configure your Conduit RPC and block explorer to be accessible through a custom domain.
Prepare your domain record
Enter a valid custom domain in Conduit to preview its required CNAME record. Conduit doesn’t save the custom domain until you add it, so you can configure and check the DNS record first.
For example, to point rpc.example.com to a Conduit RPC endpoint, the preview
looks like this:
Your DNS provider might require the full custom domain, rpc.example.com,
instead of only the subdomain, rpc. Some providers also add the trailing
dot to the value automatically.
For the fastest activation, publish the CNAME record and use Check DNS to
confirm that it’s publicly resolvable before you select Add domain.
If you select Add without verification, certificate validation starts
immediately. When the expected CNAME record isn’t publicly resolvable,
validation retries use progressively longer intervals. After you correct the
DNS record, certificate issuance can therefore take several hours and, in
some cases, up to 24 hours.
Steps
Access Settings
Navigate to your deployment dashboard. Click Settings, and then select Customization from the sidebar. Scroll down to the Custom Domains section.
Enter your custom domain
Enter your intended custom domain for your Conduit RPC or Conduit Explorer. Conduit displays the required CNAME record without saving the custom domain.
Configure the DNS record
Add the displayed CNAME record to your domain’s DNS settings. You can typically do this in your DNS provider’s control panel. DNS propagation can take up to 24 hours, depending on your provider.
Turn off the Cloudflare proxy
If you’re using Cloudflare, turn off the proxy for the subdomain you’re setting up.
Check DNS
Select Check DNS. If Conduit can’t resolve the expected CNAME record yet, wait for DNS propagation and check again.