Setting Up Domains
Step-by-step guide to configuring custom domains for your deployments
Adding a custom domain to your deployment is straightforward. This guide will walk you through the process.
- 1
Navigate to Domains
Go to Deployment → Settings → Domains or navigate to Project → Domains.Navigate to the Domains section in your deployment settings. - 2
Add Domain
Click "Add Domain" or "Connect Domain" button.Click Add Domain to start configuring a custom domain. - 3
Enter Domain
Enter your domain name (e.g., "example.com" or "app.example.com").ℹ️You can add both root domains (example.com) and subdomains (app.example.com).
Enter your domain name in the domain configuration form. - 4
Choose DNS Configuration Method
You have two options for configuring your domain:Option 1: Use Nameservers (Recommended)
Point your domain's nameservers to Hetzner. This gives Hetzner full control over your DNS and is the easiest method. See the "Configuring Nameservers" section below for detailed instructions.
Option 2: Use A/CNAME Records
Add A or CNAME records at your current DNS provider. Use this if you want to keep DNS management at your registrar or DNS provider.
Choose between nameservers or A/CNAME records for your domain configuration. - 5
Get DNS Configuration
If using A/CNAME records, Sproobo will provide DNS records you need to add:- A Record: IP address to point your domain to
- CNAME Record: Alternative DNS record (for subdomains)
- Verification Record: TXT record for domain verification
Sproobo provides DNS records you need to add to your domain provider. - 6
Configure DNS
Add the DNS records in your domain provider's DNS settings (if using A/CNAME method):DNS Configuration Steps
- Log in: Access your domain registrar or DNS provider
- Find DNS Settings: Locate DNS management or DNS records section
- Add Records: Add the A or CNAME record provided by Sproobo
- Save Changes: Save your DNS changes
Add the DNS records in your domain provider's DNS settings. - 7
Wait for DNS Propagation
Wait for DNS changes to propagate (typically 5-60 minutes, but can take up to 48 hours).ℹ️You can check DNS propagation status in Sproobo while waiting.
Monitor DNS propagation status in Sproobo. - 8
Verify Domain
Once DNS has propagated, Sproobo will automatically verify the domain and configure SSL.Sproobo automatically verifies your domain and sets up SSL. - 9
Domain Ready
Once verified, your domain will be:- Connected to your deployment
- SSL certificate automatically provisioned
- HTTPS redirect configured
- Ready to serve traffic
Your domain is now connected and serving HTTPS traffic.
Configuring Nameservers (Alternative Method)
Instead of using A or CNAME records, you can point your domain to Hetzner by configuring nameservers. This method is recommended for domains purchased from providers like GoDaddy, Namecheap, Google Domains, or any other registrar.
Using nameservers gives Hetzner full control over your domain's DNS, making it easier to manage all DNS records in one place. This is the recommended approach for most users.
Step 1: Get Your Nameservers
Point your domain's nameservers to Hetzner's nameservers:
hydrogen.ns.hetzner.comoxygen.ns.hetzner.comhelium.ns.hetzner.de
Hetzner Nameservers
Step 2: Configure Nameservers at Your Domain Provider
The exact steps vary by provider, but the general process is the same:
- 1
Log in to Your Domain Registrar
Access your domain registrar account (GoDaddy, Namecheap, Google Domains, etc.).Log in to your domain registrar account. - 2
Navigate to DNS Settings
Find the DNS or Nameserver settings for your domain. This is usually under:- Domain Settings → DNS
- Domain Management → Nameservers
- Advanced DNS → Nameservers
Navigate to the DNS or Nameserver settings for your domain. - 3
Change Nameservers
Replace the default nameservers with Hetzner's nameservers:texthydrogen.ns.hetzner.com oxygen.ns.hetzner.com helium.ns.hetzner.de
Enter Hetzner's nameservers in your domain registrar's nameserver settings. - 4
Save Changes
Save your changes. The nameserver update may take a few minutes to process.⚠️Changing nameservers can take up to 24-48 hours to fully propagate. Your domain may be temporarily unavailable during this time.
Save the nameserver changes and wait for propagation.
Provider-Specific Instructions
GoDaddy
- Log in to your GoDaddy account
- Go to "My Products" → "Domains"
- Click on your domain name
- Scroll to "Additional Settings" → "Manage DNS"
- Click "Change" next to Nameservers
- Select "Custom" and enter the three Hetzner nameservers
- Click "Save"
Namecheap
- Log in to your Namecheap account
- Go to "Domain List"
- Click "Manage" next to your domain
- Go to the "Advanced DNS" tab
- Scroll to "Nameservers" section
- Select "Custom DNS"
- Enter the three Hetzner nameservers
- Click the checkmark to save
Google Domains
- Log in to Google Domains
- Select your domain
- Click "DNS" in the left sidebar
- Scroll to "Name servers" section
- Click "Use custom name servers"
- Enter the three Hetzner nameservers
- Click "Save"
Cloudflare
- Log in to your Cloudflare account
- Select your domain
- Go to "DNS" → "Nameservers"
- Click "Change nameservers"
- Enter the three Hetzner nameservers
- Click "Continue" and confirm
Step 3: Configure Domain in Hetzner
After updating nameservers, configure your domain in Hetzner Cloud:
- 1
Access Hetzner DNS
Log in to your Hetzner Cloud console and navigate to your project. - 2
Add DNS Zone
Go to "DNS" → "Zones" and click "Add DNS Zone".Add a new DNS zone for your domain in Hetzner Cloud. - 3
Enter Domain
Enter your domain name (e.g., "example.com") and create the zone.Enter your domain name to create the DNS zone. - 4
Configure DNS Records
Add the necessary DNS records (A, CNAME, etc.) as provided by Sproobo.Add DNS records for your domain in Hetzner Cloud.
Nameservers vs. A/CNAME Records
When to Use Nameservers
- You want Hetzner to manage all DNS records
- You're setting up a new domain
- You don't need to keep other DNS records at your registrar
- You want centralized DNS management
When to Use A/CNAME Records
- You need to keep other DNS records at your current provider
- You're using a DNS provider like Cloudflare for additional features
- You want to keep your domain's DNS management at your registrar
- You need to point only specific subdomains to Hetzner
DNS Configuration Examples
Adding A Record (Root Domain)
For root domains like example.com:
Type: A
Name: @ (or blank, depending on provider)
Value: [IP address provided by Sproobo]
TTL: 3600 (or default)
Adding CNAME Record (Subdomain)
For subdomains like app.example.com:
Type: CNAME
Name: app
Value: [CNAME target provided by Sproobo]
TTL: 3600 (or default)
Multiple Domains
You can add multiple domains to a single deployment:
- 1
Add Additional Domain
Click "Add Domain" again to add another domain. - 2
Configure DNS
Configure DNS records for each additional domain. - 3
All Domains Active
All domains will be active and serve the same deployment with SSL certificates for each.View all configured domains for your deployment.
Troubleshooting DNS
Common DNS Issues
- DNS Not Propagating: Wait up to 48 hours, check DNS propagation tools
- Wrong IP Address: Verify the A record points to the correct IP
- CNAME Conflicts: Don't use CNAME for root domains, use A record
- TTL Issues: Lower TTL for faster updates during configuration
Domains Behind a Proxy (Cloudflare)
If your domain is behind a proxy such as Cloudflare (with "Proxied" / orange cloud enabled), Let's Encrypt must still reach your origin server to complete the HTTP-01 challenge for SSL certificates. If certificate issuance fails with a 404 on the ACME challenge:
- Option 1: Set the subdomain to DNS only (grey cloud) in Cloudflare during the first certificate request, then re-enable proxy after the certificate is issued.
- Option 2: Ensure the proxy forwards HTTP traffic to your origin on port 80 so the challenge file at
/.well-known/acme-challenge/can be served.
The "Domain is behind a proxy" setting in Sproobo only relaxes DNS checks (e.g. it does not require the domain to resolve to your server's IP). HTTP-01 validation still requires the challenge URL to be reachable from the internet, either directly at your origin or via the proxy.
Next Steps
Now that your domain is configured: