Custom domains for HivePods

Serve any of your pod’s addresses on your own domain, with HTTPS issued automatically: the main address (port 80), or a port you exposed, such as your API on port 5100.

1. Open the pod in the console and find the Custom domains card. Enter your domain and add it. If the pod has exposed ports, choose which address the domain serves; the default is the main address.

2. Create the two records shown at your DNS provider:

   Type	Name (host)	Value
   CNAME	app (for app.example.com)	the target shown, like web1.pods.dockhive.cloud
   TXT	_dockhive-verification.app	the verification token shown

   Each address has its own target: a domain for port 5100 on web1 points at something like web1-5100.pods.dockhive.cloud. Copy the target the console shows for that domain.

3. Click Verify. DockHive also checks every few minutes on its own. DNS changes can take up to 48 hours.

4. Once verified, the HTTPS certificate is issued and the domain shows active.

Use DNS-only records

Point the records straight at DockHive. If your DNS provider has a proxy or CDN mode, turn it off for these records, or the domain can’t get a certificate.

From the CLI

hivepod domain add web1 www.example.com              # the main address
hivepod domain add web1 api.example.com --port 5100  # an exposed port
hivepod domain verify web1 api.example.com
hivepod domain list web1
hivepod domain rm web1 api.example.com

domain add prints the records to create. Removing an exposed port also removes the domains attached to it.

Root domains (example.com): add the target as an ALIAS, ANAME or flattened CNAME record. If your provider supports none of these, point www at the target and forward the root domain to www.

Limits

• Up to 5 custom domains per pod.
• A domain can belong to only one pod or app. Verify within 72 hours of adding it, or the claim lapses.
• Up to 5 new certificates per account per day.

The same rules apply to custom domains for apps.