Skip to main content

Netlify Site Setup: Custom Domain Guide

Guide about Netlify Site Setup: Custom Domain Guide

Written by Mayank Baswal

Founder of is-cool-me · DNS & Platform Infrastructure

Mayank Baswal maintains the is-cool-me platform and writes technical guides focused on DNS configuration, subdomain infrastructure, SSL troubleshooting, deployment workflows, and platform reliability.

Reviewed by is-cool-me Technical Review
## Introduction Setting up a custom domain for a Netlify site is a crucial step in deploying a professional web application. When you create a project on is-cool-me, it's hosted on a subdomain like `myproject.is-pro.dev`. While this is great for development and testing, a custom domain like `myproject.com` or `api.myproject.com` is essential for production environments. This guide will walk you through the process of setting up a custom domain for your Netlify site, covering the prerequisites, step-by-step instructions, and common pitfalls to avoid. By the end of this guide, you'll have a comprehensive understanding of how to configure your Netlify site with a custom domain, ensuring a seamless user experience and professional branding. ## Prerequisites Before you start setting up a custom domain for your Netlify site, make sure you have the following prerequisites in place: - A Netlify account with a site already set up on a subdomain like `myproject.is-pro.dev`. - A custom domain name like `myproject.com` or `api.myproject.com` that you want to use for your site. - Access to your domain registrar's DNS settings, as you'll need to configure DNS records to point to Netlify. - Familiarity with basic DNS concepts, including A records, CNAME records, and TXT records. ## Step-by-step instructions Here's a step-by-step guide to setting up a custom domain for your Netlify site: 1. Log in to your Netlify account and navigate to your site's settings. 2. Click on "Domain management" and then "Add a custom domain". 3. Enter your custom domain name, such as `myproject.com`, and click "Verify". 4. Netlify will guide you through the process of verifying your domain ownership using a TXT record. 5. Once your domain is verified, you'll need to configure your DNS settings to point to Netlify. 6. Create a CNAME record with the name `www` and the value `myproject.netlify.app`. 7. Create an A record with the name `@` and the value `75.2.60.5`. 8. Update your DNS settings to include the new records. To automate the DNS configuration process, you can use a tool like `netlify dns` command-line interface. Here's an example of how to use it: ```bash netlify dns add myproject.com --type CNAME --name www --value myproject.netlify.app netlify dns add myproject.com --type A --name @ --value 75.2.60.5 ``` Alternatively, you can use a DNS management service like Cloudflare to manage your DNS settings. ## Configuration deep-dive When configuring your custom domain on Netlify, there are several options to consider. Here are some examples of configuration options with real values: - `api.myproject.is-pro.dev` as the API subdomain - `myproject.com` as the primary domain - `www.myproject.com` as the WWW subdomain - `blog.myproject.com` as a subdomain for a blog Here's an example of a `netlify.toml` file with custom domain configuration: ```toml [build] command = "npm run build" publish = "dist" [context.production] domain = "myproject.com" apiDomain = "api.myproject.is-pro.dev" [[redirects]] from = "https://myproject.com/*" to = "https://myproject.netlify.app/:splat" ``` In this example, the `domain` option specifies the primary domain, while the `apiDomain` option specifies the API subdomain. ## Common pitfalls and solutions Here are some common pitfalls to watch out for when setting up a custom domain on Netlify: 1. **Incorrect DNS configuration**: Make sure to configure your DNS settings correctly, including A records, CNAME records, and TXT records. * Solution: Double-check your DNS settings and use a tool like `netlify dns` to automate the configuration process. 2. **Domain verification issues**: If you're having trouble verifying your domain ownership, make sure to follow the instructions carefully. * Solution: Check your email for verification instructions and make sure to update your DNS settings correctly. 3. **SSL certificate issues**: If you're having trouble with SSL certificates, make sure to configure your SSL settings correctly. * Solution: Use a tool like Let's Encrypt to automate the SSL certificate process. 4. **Subdomain configuration issues**: If you're having trouble with subdomain configuration, make sure to configure your subdomains correctly. * Solution: Use a `netlify.toml` file to configure your subdomains and make sure to update your DNS settings correctly. 5. **Redirect issues**: If you're having trouble with redirects, make sure to configure your redirects correctly. * Solution: Use a `netlify.toml` file to configure your redirects and make sure to update your DNS settings correctly. ## Best practices Here are some best practices to keep in mind when setting up a custom domain on Netlify: - **Use a secure connection**: Make sure to use HTTPS to secure your connection and protect user data. - **Configure SSL certificates**: Use a tool like Let's Encrypt to automate the SSL certificate process. - **Optimize performance**: Use a CDN to optimize performance and reduce latency. - **Monitor analytics**: Use a tool like Google Analytics to monitor analytics and track user behavior. ## Troubleshooting section If you're having trouble with your custom domain setup, here are some diagnostic steps to follow: 1. **Check DNS settings**: Make sure your DNS settings are configured correctly, including A records, CNAME records, and TXT records. 2. **Verify domain ownership**: Make sure you've verified your domain ownership correctly. 3. **Check SSL certificates**: Make sure your SSL certificates are configured correctly. 4. **Check redirects**: Make sure your redirects are configured correctly. 5. **Check analytics**: Make sure you're tracking user behavior and monitoring analytics correctly. To debug failures, you can use a tool like `netlify logs` to view logs and diagnose issues. Here's an example of how to use it: ```bash netlify logs --site myproject --tail ``` This will show you the latest logs for your site, helping you diagnose issues and troubleshoot problems. ## Deployment scenario from operations Here's an example of a real-world deployment scenario: Let's say you're deploying a web application on `myproject.is-pro.dev` and you want to set up a custom domain `myproject.com`. You've already verified your domain ownership and configured your DNS settings correctly. You've also set up SSL certificates using Let's Encrypt and configured redirects using a `netlify.toml` file. Here's an example of a `netlify.toml` file for this deployment scenario: ```toml [build] command = "npm run build" publish = "dist" [context.production] domain = "myproject.com" apiDomain = "api.myproject.is-pro.dev" [[redirects]] from = "https://myproject.com/*" to = "https://myproject.netlify.app/:splat" ``` In this example, the `domain` option specifies the primary domain, while the `apiDomain` option specifies the API subdomain. The `redirects` option specifies the redirects for the primary domain. ## Common mistakes Here are some common mistakes to watch out for when setting up a custom domain on Netlify: * Incorrect DNS configuration * Domain verification issues * SSL certificate issues * Subdomain configuration issues * Redirect issues ## How to verify it works Here are some steps to verify that your custom domain setup is working correctly: 1. **Check DNS settings**: Make sure your DNS settings are configured correctly, including A records, CNAME records, and TXT records. 2. **Verify domain ownership**: Make sure you've verified your domain ownership correctly. 3. **Check SSL certificates**: Make sure your SSL certificates are configured correctly. 4. **Check redirects**: Make sure your redirects are configured correctly. 5. **Test the site**: Test your site to make sure it's working correctly, including all subdomains and redirects. ## Conclusion with next steps In conclusion, setting up a custom domain on Netlify requires careful configuration of DNS settings, domain verification, SSL certificates, and redirects. By following the steps outlined in this guide, you can ensure a seamless and professional user experience for your web application. Next steps include monitoring analytics, optimizing performance, and troubleshooting any issues that may arise. ## FAQ Here are some frequently asked questions about setting up a custom domain on Netlify: Q: What is the process for verifying domain ownership on Netlify? A: The process for verifying domain ownership on Netlify involves adding a TXT record to your DNS settings and following the instructions provided by Netlify. This ensures that you have control over the domain and can configure it correctly. Q: How do I configure DNS settings for my custom domain on Netlify? A: To configure DNS settings for your custom domain on Netlify, you'll need to create A records, CNAME records, and TXT records. You can use a tool like `netlify dns` to automate the configuration process. Q: What is the purpose of SSL certificates in custom domain setup on Netlify? A: SSL certificates are used to secure the connection between your site and users' browsers. They ensure that data is encrypted and protected from interception. Q: How do I troubleshoot issues with my custom domain setup on Netlify? A: To troubleshoot issues with your custom domain setup on Netlify, you can use a tool like `netlify logs` to view logs and diagnose issues. You can also check your DNS settings, verify domain ownership, and check SSL certificates to ensure everything is configured correctly. Q: What are some best practices for optimizing performance and security on Netlify? A: Some best practices for optimizing performance and security on Netlify include using a CDN, configuring SSL certificates, and monitoring analytics. You can also use a tool like Google Analytics to track user behavior and optimize your site for better performance.
Share this article Share on X Share on LinkedIn

Explore More