Custom domains in Supabase - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a custom domain to your Supabase project.

Supabase

supabase.project.addDomain('[1]')

Drag options to blanks, or click blank then click option'

Aexample.com

Bmyproject

C12345

Dapi.supabase.io

Attempts:

3 left

💡 Hint

Common Mistakes

Using project ID instead of domain name

Using API endpoint instead of domain name

You need to provide your custom domain name as a string to add it to your Supabase project.

2fill in blank

medium

Complete the code to verify your custom domain ownership in Supabase.

Supabase

await supabase.project.verifyDomain('[1]')

Drag options to blanks, or click blank then click option'

A12345

Bexample.com

Capi.supabase.io

Dmyproject

Attempts:

3 left

💡 Hint

Common Mistakes

Using project ID instead of domain name

Using API endpoint instead of domain name

Verification requires the exact custom domain name you added to your project.

3fill in blank

hard

Fix the error in the code to correctly configure SSL for your custom domain.

Supabase

supabase.project.configureSSL({ ssl: [1] })

Drag options to blanks, or click blank then click option'

Assl

Bfalse

Cenable

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Passing string 'enable' instead of boolean

Passing string 'ssl' instead of boolean

The method expects a boolean value 'true' to enable SSL on the custom domain.

4fill in blank

hard

Fill both blanks to create a DNS TXT record for domain verification.

Supabase

dnsRecords.create({ type: '[1]', value: '[2]' })

Drag options to blanks, or click blank then click option'

ATXT

BCNAME

Csupabase-verification-token

DA

Attempts:

3 left

💡 Hint

Common Mistakes

Using CNAME instead of TXT record

Using incorrect token value

Verification requires a TXT record with the Supabase verification token.

5fill in blank

hard

Fill all three blanks to update the custom domain settings with SSL and redirect enabled.

Supabase

supabase.project.updateDomain('[1]', { ssl: [2], redirectToHttps: [3] })

Drag options to blanks, or click blank then click option'

Aexample.com

Btrue

Cfalse

Dmyproject

Attempts:

3 left

💡 Hint

Common Mistakes

Using project ID instead of domain name

Setting SSL or redirectToHttps to false

You must specify the domain name, enable SSL with 'true', and enable HTTPS redirect with 'true'.

Practice

1. What is the main purpose of setting a custom domain in Supabase?

easy

A. To enable faster query execution

B. To increase database storage capacity

C. To create multiple user accounts automatically

D. To use your own website address instead of a default Supabase URL

Solution

1. Step 1: Understand what a custom domain is

   A custom domain lets you use your own website address instead of a generic one provided by a service.

2. Step 2: Relate to Supabase usage

   In Supabase, setting a custom domain means your app uses your own URL, making it look professional and branded.

3. Final Answer:

   To use your own website address instead of a default Supabase URL -> Option D

4. Quick Check:

   Custom domain = Own website address [OK]

Hint: Custom domain means your own website address [OK]

Common Mistakes:

• Thinking it increases database size
• Confusing with performance features
• Assuming it creates user accounts

2. Which DNS record type must you add to point your custom domain to Supabase?

easy

A. CNAME record

B. MX record

C. TXT record

D. SRV record

Solution

1. Step 1: Identify DNS record types for domain pointing

   CNAME records are used to alias one domain name to another, commonly used to point custom domains to services.

2. Step 2: Match with Supabase custom domain setup

   Supabase requires a CNAME record to link your custom domain to their servers.

3. Final Answer:

   CNAME record -> Option A

4. Quick Check:

   Custom domain pointing uses CNAME [OK]

Hint: Use CNAME to point domain to Supabase [OK]

Common Mistakes:

• Using MX record which is for email
• Using TXT record meant for verification
• Confusing SRV record with domain pointing

3. Given this Supabase custom domain setup snippet:

domain: "app.example.com"
records: [
  { type: "CNAME", value: "db.supabase.co" }
]

What happens when a user visits app.example.com?

medium

A. They are redirected to the Supabase database interface

B. Their browser connects to Supabase hosting for the app

C. They get an email verification prompt

D. They see a DNS error because CNAME is incorrect

Solution

1. Step 1: Understand CNAME effect

   The CNAME record points the domain to Supabase's hosting address, so requests go there.

2. Step 2: Interpret user visit behavior

   When visiting app.example.com, the browser connects to Supabase hosting serving the app, not the database interface or errors.

3. Final Answer:

   Their browser connects to Supabase hosting for the app -> Option B

4. Quick Check:

   CNAME directs browser to Supabase hosting [OK]

Hint: CNAME points domain to hosting, not email or errors [OK]

Common Mistakes:

• Confusing database interface with hosting
• Assuming DNS error from correct CNAME
• Thinking email verification appears on visit

4. You set a custom domain in Supabase but get a security warning in browsers. What is the most likely cause?

medium

A. You did not add an MX record

B. You used an invalid domain name format

C. You forgot to enable SSL for the custom domain

D. You set the CNAME to the wrong IP address

Solution

1. Step 1: Identify cause of browser security warnings

   Security warnings usually happen when SSL (secure connection) is missing or invalid.

2. Step 2: Relate to Supabase custom domain setup

   Supabase requires enabling SSL for custom domains to avoid browser warnings.

3. Final Answer:

   You forgot to enable SSL for the custom domain -> Option C

4. Quick Check:

   Missing SSL causes browser security warnings [OK]

Hint: Always enable SSL for custom domains [OK]

Common Mistakes:

• Confusing MX record with SSL
• Thinking domain format causes security warning
• Assuming CNAME IP address is used instead of hostname

5. You want to set up a custom domain dashboard.myapp.com for your Supabase project. Which steps must you follow to ensure it works correctly and securely?

hard

A. Buy the domain, add a CNAME DNS record pointing to Supabase, then enable SSL in Supabase settings

B. Buy the domain, add an MX record pointing to Supabase, then enable SSL in Supabase settings

C. Buy the domain, add a TXT record for verification, then disable SSL to avoid errors

D. Buy the domain, add an A record pointing to Supabase IP, then skip SSL setup

Solution

1. Step 1: Purchase domain and configure DNS

   First, buy your domain (dashboard.myapp.com) and add a CNAME record pointing to Supabase's domain to route traffic correctly.

2. Step 2: Enable SSL for secure connections

   Then, enable SSL in Supabase settings to secure the connection and avoid browser warnings.

3. Final Answer:

   Buy the domain, add a CNAME DNS record pointing to Supabase, then enable SSL in Supabase settings -> Option A

4. Quick Check:

   Domain + CNAME + SSL = Correct setup [OK]

Hint: Domain + CNAME + SSL = working custom domain [OK]

Common Mistakes:

• Using MX or TXT records incorrectly
• Skipping SSL causing security warnings
• Using A record instead of CNAME for Supabase