Custom domains in Supabase - Step-by-Step Execution

Process Flow - Custom domains

User owns domain

↓

Add domain to Supabase project

↓

Supabase provides DNS records

↓

User updates DNS provider with records

↓

DNS propagates changes

↓

Supabase verifies domain

↓

Domain active

The user adds their domain to Supabase, updates DNS records as instructed, then Supabase verifies the domain to activate it.

Execution Sample

Supabase

1. Add domain example.com in Supabase
2. Supabase shows DNS records
3. Update DNS provider with records
4. Wait for DNS propagation
5. Supabase verifies domain
6. Domain becomes active

This sequence shows how a user sets up a custom domain in Supabase step-by-step.

Process Table

Step	Action	Input/Condition	Result	Next Step
1	User adds domain	Domain = example.com	Supabase accepts domain	Supabase shows DNS records
2	Supabase provides DNS records	Records for example.com	User sees records to add	User updates DNS provider
3	User updates DNS	Adds records to DNS provider	DNS records set	Wait for DNS propagation
4	Wait for DNS propagation	DNS changes propagate	Propagation in progress	Supabase verifies domain
5	Supabase verifies domain	Checks DNS records	Records correct?	Yes -> Domain active; No -> Wait or fix DNS
6	Domain status	Verified	Domain active and serving	End
7	Domain status	Not verified	Domain inactive	User fixes DNS and retries

💡 Domain becomes active when DNS records are verified by Supabase.

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	Final
domain	none	example.com	example.com	example.com	example.com
dns_records_set	false	false	true	true	true
dns_verified	false	false	false	true/false	true (active) or false (inactive)
domain_status	none	pending	pending	verified or not	active or inactive

Key Moments - 3 Insights

Why does the domain stay inactive after adding DNS records?

Because DNS propagation takes time; Supabase verification (step 5) only succeeds after propagation completes, as shown in execution_table row 4 and 5.

What happens if DNS records are incorrect?

Supabase verification fails (execution_table row 7), so the domain remains inactive until DNS records are fixed.

Why must the user update DNS records at their DNS provider?

Supabase cannot change DNS records itself; the user must add the provided records to their DNS provider for verification and activation (execution_table row 3).

Visual Quiz - 3 Questions

Look at the execution table, at which step does Supabase check if DNS records are correct?

A Step 5

B Step 4

C Step 2

D Step 3

💡 Hint

Check the 'Action' and 'Result' columns in execution_table row 5.

According to variable_tracker, what is the value of 'dns_records_set' after Step 3?

A false

B none

C true

D pending

💡 Hint

Look at the 'dns_records_set' row under 'After Step 3' in variable_tracker.

If DNS propagation is not complete, what will be the domain status according to execution_table?

A active

B pending

C inactive

D verified

💡 Hint

Refer to execution_table row 4 and the 'domain_status' variable in variable_tracker.

Concept Snapshot

Custom domains in Supabase:
1. Add your domain in Supabase project.
2. Supabase gives DNS records to add at your DNS provider.
3. Update DNS records and wait for propagation.
4. Supabase verifies DNS records.
5. Once verified, domain becomes active.

Full Transcript

To use a custom domain with Supabase, you first add your domain name in the Supabase project settings. Supabase then provides specific DNS records that you must add at your domain's DNS provider. After updating these DNS records, you wait for the changes to propagate across the internet. Supabase periodically checks these DNS records to verify ownership and correctness. When verification succeeds, your custom domain becomes active and serves your Supabase project. If verification fails, you need to check and fix your DNS records. This process ensures your domain is properly linked and secure.