Skip to main content

Connect Vercel to an is-pro.dev Subdomain

Step-by-step DNS records and verification flow for Vercel deployments. Includes CNAME setup, SSL provisioning, and common error fixes.

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

What You Will Learn

  • How to configure DNS records for Vercel 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 Vercel account (free tier available)
  • Access to your Vercel project settings
  • Basic understanding of DNS concepts

Background Information

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

Important: Before starting, ensure you have registered your subdomain on the is-cool-me dashboard and have access to modify its DNS records.

Step-by-Step Setup

Step 1: Prepare Your Vercel Project

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

  1. Log in to your Vercel 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 Vercel

In the Vercel dashboard:

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

Tip: Make sure to use the full subdomain including your username. For example, if your username is "johndoe" and you want "myapp", use "myapp.johndoe.is-pro.dev".

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.vercel-dns.com

Important DNS Configuration:

Example of expected DNS record:

Name: myapp
Type: CNAME
Value: cname.vercel-dns.com
TTL: 300

Step 4: Verify Domain Configuration

Back in the Vercel 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 Vercel, 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 Vercel project
  3. Verify the SSL certificate is valid
  4. Test with different browsers and devices

Pro Tip: Use dig or nslookup to verify DNS propagation:

dig myapp.yourname.is-pro.dev

Troubleshooting

Common Errors and Fixes

1. Domain Not Found Error

Problem: Vercel 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.vercel-dns.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 Vercel 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 Vercel to use custom domains?

No, Vercel'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 Vercel projects?

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

What happens if I delete my Vercel project?

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

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

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

Related Guides

Conclusion

Connecting Vercel 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 Vercel'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 startup moved a staging app to Vercel and kept an old A record active, causing mixed traffic between old and new origins.

Platform nuance: Vercel domain validation may pass before all recursive resolvers refresh, so test from at least two public resolvers.

Common mistakes

  • Keeping legacy A/AAAA records when switching to Vercel CNAME targets.
  • Marking DNS as complete before Vercel reports valid configuration.
  • Forgetting to verify HTTPS certificate readiness after DNS changes.

How to verify it works

  1. Run `dig your-subdomain.is-pro.dev CNAME +short` and confirm `cname.vercel-dns.com` pathing.
  2. Check Vercel domain status is `Valid Configuration`.
  3. Open the final HTTPS URL and confirm no certificate warning appears.
Use these checks before announcing a DNS change as complete to your team.