Skip to main content

Custom Domains

Use your own domain names for a professional, branded experience.

Overview​

SailOps gateways require custom domains - there are no default subdomains provided. This gives you full control over your branding and DNS configuration from day one.

Benefits​

  • Full branding control - Use your own domain from the start
  • SEO optimization - Your domain builds your search ranking
  • User trust - Customers recognize your brand
  • Email integration - Match your email domain

Adding a Custom Domain​

Prerequisites​

  • A registered domain name
  • Access to your domain's DNS settings
  • A gateway created in your project

Step-by-Step Guide​

1. Navigate to Your Gateway​

  1. Go to Gateways
  2. Click on your gateway
  3. Click the Domains tab

2. Add Your Domain​

  1. Click Add Domain
  2. Enter your hostname (e.g., app.example.com)
  3. Select the protocol: HTTPS, TLS, or TCP
  4. Configure the port (default: 443 for HTTPS/TLS)
  5. Click Add

3. Configure DNS​

SailOps provides an IP address for your gateway. Configure your DNS using an A record:

For subdomains:

Type: A
Name: app
Value: <IP-address-from-gateway-details>
TTL: 300

For apex domains:

Type: A
Name: @
Value: <IP-address-from-gateway-details>
TTL: 300
Gateway IP Address

After creating your gateway, the IP address is displayed in your gateway details page.

4. Domain Verification​

SailOps automatically checks your DNS configuration. Once the A record is detected pointing to your gateway IP, the SSL certificate is automatically provisioned. No manual verification step is needed.

DNS Configuration Examples​

Cloudflare​

Type: A
Name: app
Content: <IP-address-from-gateway-details>
Proxy status: DNS only (gray cloud)
TTL: Auto
Cloudflare Proxy

Initially set to "DNS only" for verification. You can enable proxy after SSL is provisioned.

Route 53 (AWS)​

Record name: app.example.com
Record type: A
Value: <IP-address-from-gateway-details>
TTL: 300
Routing policy: Simple

GoDaddy​

Type: A
Host: app
Points to: <IP-address-from-gateway-details>
TTL: 1 hour

Namecheap​

Type: A Record
Host: app
Value: <IP-address-from-gateway-details>
TTL: Automatic

Squarespace Domains (formerly Google Domains)​

Host name: app
Type: A
TTL: 300
Data: <IP-address-from-gateway-details>

Apex Domains​

Apex domains (e.g., example.com without www) use the same A record configuration:

Type: A
Name: @
Value: <IP-address-from-gateway-details>
TTL: 300
IP Address

The IP address is displayed in your gateway details page.

Domain Status​

DNS Status​

Each domain shows its current DNS and TLS status:

StatusDescription
DNS Configured (green)A record correctly points to gateway IP
DNS Not Configured (red)A record missing or incorrect
TLS Ready (green)SSL certificate is valid and active
TLS Not Ready (red)Certificate pending or provisioning issue

Troubleshooting DNS​

DNS not propagated yet

  • Wait 5-10 minutes for propagation
  • Use dig or online tools to check
# Check A record
dig app.example.com A

Wrong DNS value

  • Double-check the IP address matches your gateway
  • Ensure no typos in the IP address

Proxy enabled (Cloudflare)

  • Temporarily disable proxy (orange cloud → gray cloud)
  • Re-enable after SSL is provisioned

Wildcard Domains​

Setting Up Wildcards​

Route all subdomains to your gateway:

Type: A
Name: *
Value: <IP-address-from-gateway-details>

This allows:

  • api.example.com
  • app.example.com
  • staging.example.com
  • Any *.example.com

Adding Wildcard in SailOps​

  1. Add domain as *.example.com
  2. Configure wildcard DNS record
  3. SSL covers all subdomains

Multiple Domains​

Adding Multiple Domains​

A single gateway can serve multiple domains:

Domains:
- example.com
- www.example.com
- app.example.com
- api.example.com
- myotherapp.com

Domain-Specific Routing​

Route different domains to different containers:

routes:
- host: api.example.com
path: /
container: api
port: 8080
- host: app.example.com
path: /
container: frontend
port: 3000
- host: "*" # Default for all other domains
path: /
container: landing
port: 80

Domain Management​

Viewing Domain Status​

  1. Go to your gateway
  2. Click Domains tab
  3. View status of each domain

Removing a Domain​

  1. Find the domain in the list
  2. Click Delete
  3. Confirm deletion
warning

Deleting a domain immediately stops traffic on that domain.

DNS Best Practices​

Use Subdomains​

Prefer app.example.com over example.com:

  • Cleaner organization of services
  • Easier to manage multiple services
  • Simpler SSL provisioning

Low TTL During Setup​

Use low TTL (300 seconds) during initial setup:

  • Faster propagation
  • Quick updates if changes needed
  • Increase TTL after stable

Backup DNS Records​

Before making changes:

  1. Document existing records
  2. Test changes in staging
  3. Have rollback plan ready

Troubleshooting​

Domain Not Resolving​

# Check if DNS is configured
dig app.example.com A

# Expected output shows A record with your gateway IP
;; ANSWER SECTION:
app.example.com. 300 IN A <your-gateway-ip>

SSL Certificate Not Provisioning​

  1. Verify domain is verified
  2. Check DNS is correct
  3. Wait up to 10 minutes
  4. Contact support if issue persists

"Too Many Redirects"​

Usually caused by:

  • HTTPS redirect loop with an external proxy
  • Conflicting redirect rules

Solution:

  • Check any external proxy SSL/TLS settings
  • Verify redirect configuration

Domain Works, But Slow​

  1. Check DNS TTL (lower = more lookups)
  2. Check gateway latency and HTTP traffic metrics
  3. Check container performance