Custom Domains

Custom domains let you serve your applications from your own domain names instead of Reoclo-provided subdomains. Reoclo handles DNS verification, SSL certificate provisioning, and continuous monitoring to keep your domains healthy.

Prerequisites

Before adding a custom domain:

• DNS access: You need the ability to add TXT records to your domain’s DNS settings.
• Admin role: Only admins can add, verify, or delete domains.
• Application deployed (optional): You can add domains before or after deploying an application. If you add a domain before deployment, you can link it to an application later.

Adding a Domain

1. Navigate to Domains

   From the dashboard, go to Servers → Domains.

2. Add a new domain

   Click Add Domain and enter your fully qualified domain name (FQDN):

   app.example.com

   Or use an apex domain:

   example.com

3. Link to an application (optional)

   If you want this domain to route to a specific application, select it from the dropdown. You can skip this step and link the domain later.

4. Save the domain

   Click Add Domain. Reoclo generates a verification token and displays DNS instructions.

Verifying Your Domain

After adding a domain, you must verify ownership by adding a TXT record to your DNS settings.

1. Copy the verification token

   Reoclo shows a verification token in the domain detail view:

   reoclo-verification=abc123def456...

2. Add a TXT record to your DNS

   In your DNS provider’s control panel (Cloudflare, Route 53, Namecheap, etc.), add a TXT record:

   Type	Name	Value
   TXT	_reoclo-verify.app.example.com	reoclo-verification=abc123def456...

   If you’re verifying an apex domain (example.com), the name is _reoclo-verify.example.com.

   Tip

   DNS propagation can take 5-60 minutes depending on your provider. Use a tool like dig to check if the record is live:

   dig TXT _reoclo-verify.app.example.com +short

   You should see the verification token in the output.

3. Trigger verification

   Once the TXT record is live, return to the domain detail view in the Reoclo dashboard and click Verify Domain.

   Reoclo checks your DNS records. If the token matches, the domain status changes to Verified.

4. Point your domain to Reoclo

   After verification, add an A or CNAME record to route traffic to your Reoclo server:

   Type	Name	Value
   A	app.example.com	<your-server-ip>

   Or use a CNAME if your DNS provider supports it for subdomains:

   Type	Name	Value
   CNAME	app.example.com	<your-reoclo-hostname>

   Caution

   Most DNS providers do NOT allow CNAME records on apex domains (example.com). Use an A record instead, or check if your provider supports CNAME flattening (Cloudflare does).

Monitoring

After verification, Reoclo continuously monitors your domain’s health across three dimensions.

DNS Status

Checks if your domain resolves correctly to the expected IP address.

• Resolving: DNS lookup in progress.
• Resolved: Domain points to the correct server.
• Misconfigured: Domain points to the wrong IP or doesn’t resolve.

If DNS status shows Misconfigured, check your A or CNAME record in your DNS provider.

SSL Status

Tracks SSL certificate provisioning and validity.

• Provisioning: Certificate is being requested.
• Active: Certificate is valid and not expiring soon.
• Expired: Certificate has expired. Reoclo will attempt to renew automatically.
• Error: Certificate provisioning failed (usually due to DNS misconfiguration).

Note

SSL certificates are provisioned automatically after DNS verification. This can take 1-5 minutes. If provisioning fails, check that your domain resolves correctly and that port 80 is accessible on your server for the certificate challenge.

Uptime Status

Monitors HTTP availability of your domain.

• Up: Domain responds to HTTP requests.
• Down: Domain is unreachable.
• Degraded: Intermittent failures or slow response times.

Updating a Domain

You can update a domain’s linked application or disable it temporarily.

1. Go to Servers → Domains and select the domain.
2. Click Edit.
3. Change the linked application or toggle the domain status to Disabled.
4. Click Save.

Disabling a domain stops traffic routing but keeps the domain record and monitoring data. Re-enable it anytime by setting the status back to Active.

Deleting a Domain

Deleting a domain soft-deletes it. The domain record is retained for audit purposes but no longer routes traffic or appears in the domain list.

1. Go to Servers → Domains and select the domain.
2. Click Delete Domain.
3. Confirm the deletion.

Caution

After deletion, you can re-add the domain, but you’ll need to verify it again with a new TXT record.

Troubleshooting

Verification Fails with “TXT Record Not Found”

Cause: The TXT record hasn’t propagated yet, or the record name is incorrect.

Fix:

1. Wait 5-10 minutes and try again
2. Check the record name: it must be _reoclo-verify.<your-domain>, not just <your-domain>
3. Use dig to verify the record is live:

   dig TXT _reoclo-verify.app.example.com +short

Verification Token Expired

Cause: Verification tokens expire after 30 days.

Fix:

1. Delete the domain and re-add it to generate a new token
2. Update the TXT record with the new token and verify again

SSL Status Stuck on “Provisioning”

Cause: The certificate challenge can’t reach your domain. Common reasons: DNS doesn’t resolve to the correct server, port 80 is blocked, or the application isn’t deployed.

Fix:

1. Check DNS status first. If it’s Misconfigured, fix your A/CNAME record
2. Ensure port 80 is open on your server:

   sudo ufw status

   If port 80 is blocked:

   sudo ufw allow 80/tcp

3. Verify the application is deployed and running in Applications → Deployments

Domain Shows “Down” in Uptime Monitoring

Cause: The application isn’t responding to HTTP requests, or the server is unreachable.

Fix:

1. Check the application deployment status. If the deployment failed, redeploy
2. Check if the container is running on the server (use the terminal in the dashboard or the reoclo/run action):

   docker ps

3. Check server health in Servers. If the server is Unreachable, investigate network connectivity

DNS Status Shows “Misconfigured”

Cause: The A record points to the wrong IP, or DNS hasn’t propagated yet.

Fix:

1. Verify the A record value matches your server’s IP address (check the server detail page in the dashboard)
2. Wait 5-10 minutes for DNS propagation
3. Use dig to check current resolution:

   dig app.example.com +short

   The output should match your server’s IP

Next Steps

• Deploy an application to serve traffic on your custom domain
• Set up a status page to display domain uptime publicly
• Learn about encryption and how Reoclo protects your data