Connect a custom domain
Attach a customer-controlled hostname and verify DNS and certificate state before promoting it.
Last updated 2026-08-07
What you'll achieve
- Serve a project on a trusted hostname
- Verify DNS ownership and certificate readiness
- Avoid routing traffic before the domain is healthy
Before you start
Custom domains are plan-governed. The domain must belong to the active workspace, and you must be able to edit its DNS records.
Connect the domain
Open the project Domains page, add the hostname, and copy the exact DNS records BlinkHost displays. Add those records at the DNS provider without changing their names or values. DNS remains customer-managed unless a separate provider integration explicitly says otherwise.
Verify
Wait for the dashboard to confirm ownership, routing, and certificate readiness. Do not remove an existing production route until the BlinkHost hostname is healthy. Test HTTPS and the intended host before announcing the change.
Certificate or DNS changes can take time to propagate. Repeatedly deleting and recreating the domain usually makes diagnosis harder.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.