Next.js Discord

Discord Forum

Domain not resolving properly

Unanswered
Island Scrub-Jay posted this in #help-forum
Open in Discord
Island Scrub-JayOP
Hello guys,

I added a custom domain to my project but most times it does not open the site using https://leetano.com but is accessible using https://www.leetano.com and the Vercel domain https://leetano-v2.vercel.app.

I have been experiencing this issue with all of my projects using a custom domain from different domain providers and my DNS is properly configured.

The domain providers told me the problem is from Vercel and I've contacted your support severally about this issue and the problem is yet to be solved.

Please kindly assist.

24 Replies

@joulev all three domains work fine for me
Island Scrub-JayOP
Sometimes it resolves but it doesn't work most of the time.
@Island Scrub-Jay Sometimes it resolves but it doesn't work most of the time.
im pretty sure it's just your device's outdated dns cache. restarting the device should work.

i can access https://leetano.com 100% of the time. it always redirects to www.leetano.com as expected.
see ^ discord themselves can access the domain perfectly fine, that's why the embed worked
@joulev im pretty sure it's just your device's outdated dns cache. restarting the device should work. i can access https://leetano.com 100% of the time. it always redirects to www.leetano.com as expected.
Island Scrub-JayOP
It wasn't resolving at the time I made the post but I can see it is working now. Any idea the cause of the downtime without adding www?
@Island Scrub-Jay It wasn't resolving at the time I made the post but I can see it is working now. Any idea the cause of the downtime without adding www?
each device including the phone or computer you are using right now has a dns cache. probably when you tried to access leetano.com, the device still had an outdated and erroneous dns cache that's why you couldn't resolve the domain. this typically happens whenever you switch the dns record of the domain.

anyway that's just a cache issue that resolves itself quite quickly. your users shouldn't be affected because they didn't access your domain before you switch the dns records hence they didn't have outdated information on your domain dns.
the dns cache is not on the browser, it's on the operating system. restarting the device should work. or it should just fix itself after a while, devices don't store the cache for long.
Island Scrub-JayOP
I've been expressing this issue for months now
what, months? that's weird
well then im out of idea, sorry. the domain works fine for me.
Island Scrub-JayOP
Please have a look at the DNS configuration from Namecheap.
Island Scrub-JayOP
The domain is currently not responding at this timestamp 1721794430
Island Scrub-JayOP
@joulev Hello, after several debugging I noticed the site opens if I turn on my VPN during the downtime. What do you think?
@Island Scrub-Jay <@484037068239142956> Hello, after several debugging I noticed the site opens if I turn on my VPN during the downtime. What do you think?
my only guess is that your ISP blocked 76.76.21.21, i.e. they blocked Vercel. i know quite some governments blocking *.vercel.app domains, but i don't know of any governments blocking the 76.76.21.21 IP specifically
to check if the ISP blocked 76.76.21.21, check if you can access https://nextjs-faq.com. that domain also goes to 76.76.21.21.
@joulev to check if the ISP blocked 76.76.21.21, check if you can access https://nextjs-faq.com. that domain also goes to 76.76.21.21.
Island Scrub-JayOP
I'm able to access https://nextjs-faq.com and vercel.app domains without any issues. The problem is the downtimes using the added custom domain.
then i don't have any clues, sorry
Island Scrub-JayOP
It's just weird and might be a Vercel thing.
but if u turn off vpn u will get the same issue
did u try moving from namecheap to cloudflare?
migrate your nameservers to cloudflare, and try again. is there a specific reason u use www as cname?