Custom domains and HTTPS
Add your own hostnames to a public web service or static site. The generated Infralane address remains available alongside custom domains.
Before you begin
You need project write permission, a live deployment with no deployment pending, access to the domain’s DNS settings and a server reachable on ports 80 and 443. Workers and TCP/UDP-only services do not use HTTP domains.
Add the hostname
Open the application’s Domains page. Enter a hostname such as app.example.com, without a protocol, path or port, then select Add domain. Add the apex domain and www separately if you want both. Wildcards are not supported.
The new record starts as Pending. Adding it does not yet connect traffic or issue a certificate.
Set the DNS records
Copy the exact records displayed by the dashboard:
| Record | Purpose | Value |
|---|---|---|
| A | Route the hostname to your server | The pool IPv4 address shown by Infralane |
| TXT | Verify ownership of this hostname | The displayed _infralane name and verification value |
Your DNS provider may expect names relative to the zone. Use DNS-only mode, remove conflicting A records and remove AAAA records for this hostname. Keep the ownership TXT record for future checks.
Verify and connect
Wait for DNS propagation, then select Verify and connect. Infralane checks the routing address and ownership record before configuring the route on your server.
Test HTTPS
Open the hostname after it is connected. Crane’s web proxy handles certificate requests and renewals. Connected confirms routing; certificate issuance can still fail because of DNS policy, certificate-authority limits or ports that are not reachable.
DNS verification fails
Check the exact hostname, A address and TXT value shown in the dashboard. Ensure public DNS sees them, remove conflicting IPv6 or old addresses, and allow time for propagation before retrying. A failed check preserves the pending domain and its error.
If a node upgrade is required, update Crane and retry. Do not disable certificate checks in your browser to work around a failed HTTPS connection.
Remove a domain
Select the hostname’s removal action and review the confirmation. Removing it stops Infralane routing for that hostname and leaves the generated application address intact. Infralane does not delete DNS records at your provider; clean those up separately when appropriate. A failed removal remains available for retry.
Remove custom domains before moving the application to another pool or disabling its public networking. Domain changes do not rebuild or redeploy the application.