Connect Netlify to an is-pro.dev Subdomain

What You Will Learn

• How to configure DNS records for Netlify deployments
• Setting up custom domains with SSL certificates
• Verifying domain ownership with is-pro.dev
• Common errors and how to fix them
• Best practices for production deployments

Requirements

• A verified is-pro.dev subdomain
• A Netlify account (free tier available)
• Access to your Netlify project settings
• Basic understanding of DNS concepts

Background Information

When deploying applications on Netlify, you can use a custom domain like myapp.yourname.is-pro.dev instead of the default Netlify subdomain. This guide will walk you through connecting your Netlify project to an is-pro.dev subdomain.

Step-by-Step Setup

Step 1: Prepare Your Netlify Project

Before configuring DNS, ensure your project is ready to receive the custom domain:

1. Log in to your Netlify account
2. Navigate to your project dashboard
3. Go to the project settings by clicking the "Settings" tab
4. In the left sidebar, click on "Domains"

Step 2: Add Your Custom Domain in Netlify

In the Netlify dashboard:

1. Click "Domain Settings"
2. Enter your full subdomain (e.g., myapp.yourname.is-pro.dev)
3. Click "Add"

Step 3: Configure DNS Records in is-cool-me Dashboard

Now you need to add the required DNS records:

1. Log in to the is-cool-me dashboard
2. Select your subdomain from the list
3. Click "Add Record"
4. Add a CNAME record with:
   • Name: your subdomain prefix (e.g., "myapp")
   • Type: CNAME
   • Value: cname.netlify.com

Name: myapp
Type: CNAME
Value: cname.netlify.com
TTL: 300

Step 4: Verify Domain Configuration

Back in the Netlify dashboard:

1. Check the domain status - it should show "Valid Configuration"
2. If it shows "Verifying", wait a few minutes and refresh
3. If there are errors, check the troubleshooting section below

Step 5: Update Your Project Settings

Ensure your project is configured correctly:

1. In Netlify, go to your project settings
2. Under "Domains", make sure your custom domain is listed
3. Check that SSL certificates are automatically provisioned

Verification

To verify your setup is working correctly:

1. Visit your custom domain in a browser (e.g., https://myapp.yourname.is-pro.dev)
2. Check that it loads your Netlify project
3. Verify the SSL certificate is valid
4. Test with different browsers and devices

dig myapp.yourname.is-pro.dev

Troubleshooting

Common Errors and Fixes

1. Domain Not Found Error

Problem: Netlify shows "Domain not found"

Cause: DNS records not propagated yet or incorrect CNAME value

Solution:

• Wait 5-10 minutes for DNS propagation
• Verify CNAME value is exactly cname.netlify.com
• Check for typos in the subdomain name

2. SSL Certificate Pending

Problem: SSL certificate shows as "Pending"

Cause: Normal delay in certificate issuance

Solution:

• Wait up to 24 hours for automatic SSL provisioning
• Ensure your DNS records are correct
• Check that you're not using conflicting A records

3. CNAME Loop Error

Problem: Error about CNAME loops

Cause: Conflicting DNS records

Solution:

• Remove any A records for the same subdomain
• Ensure only one CNAME record exists for the subdomain
• Wait for DNS propagation after making changes

4. DNS Propagation Delays

Problem: Changes not reflecting immediately

Cause: DNS caching across global servers

Solution:

• Wait 5-30 minutes for propagation
• Use dig @8.8.8.8 to check Google's DNS
• Clear your local DNS cache

Best Practices

• Use descriptive subdomain names: Instead of "app1", use "dashboard" or "api"
• Set appropriate TTL values: Use lower TTL (300s) during setup, higher (3600s) for production
• Monitor certificate expiration: Although Netlify auto-renews, it's good to be aware
• Keep DNS records organized: Add comments to explain each record's purpose
• Test before production: Use a staging subdomain first

FAQ

Do I need to pay for Netlify to use custom domains?

No, Netlify's free tier includes custom domains and automatic SSL certificates.

How long does DNS propagation take?

Typically 5-30 minutes, but can take up to 24 hours in rare cases.

Can I use the same subdomain for multiple Netlify projects?

No, each subdomain can only point to one target. You'll need separate subdomains.

What happens if I delete my Netlify project?

Visitors will see a Netlify error page. Remember to remove the DNS record to prevent takeover risks.

How do I redirect www to non-www (or vice versa)?

Netlify handles this automatically. Add both versions as custom domains in your project settings.

Related Guides

• Connect Vercel to an is-pro.dev Subdomain
• Set Up GitHub Pages with a Custom Subdomain
• Diagnose SSL Pending on a New Subdomain
• Migrate a Subdomain Between Hosting Providers

Conclusion

Connecting Netlify to your is-pro.dev subdomain is straightforward when you follow these steps. The key is ensuring your DNS records are correctly configured and allowing time for propagation. With automatic SSL certificates and the flexibility of Netlify's platform, you'll have a professional deployment in minutes.

Remember to monitor your domain's performance and update records as needed. For any issues not covered in this guide, check the blog for more detailed troubleshooting posts or join our Discord community for real-time support.

Deployment scenario from operations

A docs site moved to Netlify but retained an old redirect configuration that bounced users to an outdated host.

Common mistakes

• Leaving conflicting redirects active while changing DNS targets.
• Using an incorrect CNAME target copied from another project.
• Not checking final host header behavior after deployment.

How to verify it works

1. Confirm CNAME target with `dig` against authoritative and public resolvers.
2. Run `curl -I` on final URL and verify single-hop redirect behavior.
3. Confirm Netlify serves the correct deploy preview and production domain.