Which of the following best describes the first step to configure a custom domain for your Supabase project?
Think about what needs to be done both in Supabase and your DNS provider to link your domain.
To use a custom domain, you must first add it in the Supabase dashboard. Supabase then provides DNS records you must add to your DNS provider to point your domain to Supabase.
You want to point your custom domain app.example.com to your Supabase project. Which DNS record type should you use to correctly configure this?
Think about which DNS record type points a subdomain to another domain.
A CNAME record maps a subdomain to another domain name, which is required to point your custom domain to your Supabase project URL.
When you add a custom domain to your Supabase project, how is SSL (HTTPS) handled to secure your domain?
Consider how modern cloud services simplify HTTPS setup for custom domains.
Supabase uses Let's Encrypt to automatically create and renew SSL certificates for your custom domains, so you don't have to manage certificates manually.
After adding your custom domain and updating DNS records, you notice your domain is not immediately accessible. What is the expected behavior during this period?
Think about how DNS changes work on the internet.
DNS changes take time to spread across the internet. During this time, your domain may not resolve correctly or may show cached content until propagation finishes.
Which DNS configuration practice enhances security when setting up a custom domain for your Supabase project?
Consider how to protect DNS records from being altered by attackers.
DNSSEC adds a layer of security by digitally signing DNS records, preventing attackers from redirecting your domain to malicious sites.