Skip to main content

Troubleshooting Custom Domain Access

Written by Benjamin Dell

If a custom domain stops opening your event, use the event’s original HeySummit subdomain to reach the dashboard while you check the DNS and validation status.


​

Open the domain settings

  1. Sign in through the event’s original HeySummit address. If you cannot find it, contact [email protected] with the event name and account details in a private request.

  2. Go to Event Settings > Branding and Site Settings > Event Domain. The HeySummit Domain option shows the included event address.

  3. Select Custom Domain to inspect the configured address and status.


​

Check DNS and validation

  1. Confirm the CNAME record for your chosen event subdomain points to fallback.heysummit.com, rather than another event’s HeySummit subdomain.

  2. Follow the custom domain setup guide and add every TXT verification record shown by HeySummit. Copy the current names and values exactly.

  3. If the domain is already registered, use Refresh Status to check progress. If HeySummit is still preparing TXT records, wait a few minutes and refresh again.

  4. If HeySummit shows an updated-record notice, replace previous TXT values with the current values displayed. There is no single deadline in this guide that replaces the current instructions shown for your domain.


​

DNS changes can take a few minutes or longer to be detected. A custom domain becomes active after the required DNS checks and SSL activation complete. If a certificate error persists, check CAA record conflicts and ask your DNS provider for help with records you cannot configure.


​

Return to the HeySummit address

If you deliberately want to stop using the custom domain, select HeySummit Domain and Save. This removes the direct custom-domain connection; share the HeySummit address with anyone who needs to visit the event. You do not need to remove the connection merely to inspect its status. If validation still fails, contact support with the event address, custom hostname, exact error and a screenshot of the status. Keep account credentials and unrelated DNS information private.

Did this answer your question?