getting DNS_PROBE_FINISHED_NXDOMAIN on my custom domain

[sunny0183]

Works fine on localhost:3000, i can create sites (subdomains) and posts on those sites and visit each of those posts using their subdomain on localhost.

But after deploy on vercel using the public domain (ad3535.com) the only thing works is the landing page on https://ad3535.com that says "Edit this page on app/home/page.tsx". Any attempt to go to https://app.ad3535.com throws DNS_PROBE_FINISHED_NXDOMAIN.

On vercel project i have below environment variable for the root domain NEXT_PUBLIC_ROOT_DOMAIN=ad3535.com

and i added the domain ad3535.com (A pointing to 76.76.21.21) and *.ad3535.com by changing the nameservers to vercel name servers and it has been 2 days but the DNS is still not resolving, reboot PC and flush dns done several times.

So dns resolves with https://ad3535.com but not with wildcard domains (https://app.ad3535.com or https://pleasework.ad3535.com)

Any ideas??

UPDATE: The site does work using mobile broadband so it seems my ISP is blocking subdomains. My ISP is CommunityFiber in UK. Has any one got similar problem? can you share your experience here please?

[itstrevinooo]

Hey @sunny0183,

I had the same issue, after struggling for a bit I realized that the domain redirect was the issue. You must point your www.yourdomain.com to yourdomain.com and add *.yourdomain.com.

It worked for me, hopefully it works for you as well.

[sangyookm]

Hey @sunny0183,

I had the same issue, after struggling for a bit I realized that the domain redirect was the issue. You must point your www.yourdomain.com to yourdomain.com and add *.yourdomain.com.

It worked for me, hopefully it works for you as well.

Could you elaborate a bit more? I've run into the same issue

[daylonball]

Hey @sunny0183, I had the same issue, after struggling for a bit I realized that the domain redirect was the issue. You must point your www.yourdomain.com to yourdomain.com and add *.yourdomain.com. It worked for me, hopefully it works for you as well.

Could you elaborate a bit more? I've run into the same issue

Did you ever figure this out? I am getting this at the moment as well.

EDIT: I had everything configured correctly I was just being impatient and not waiting for my nameservers to propagate to vercel. Once they did after about 3 hours it was resolved and working.