Not resolving DNS on my country (Brazil)

Help
1

Hi, suddenly, few hours ago, my dns stoped to work in my country, I can’t access anymore bolaoless.com. Now I only can access subdomains like app.bolaoless.com and back.bolaoless.com

I was expecting to access the site regularly,

┌───────────────────────────────────────
├─────── Output of bolaoless.com

  • Host bolaoless.com:443 was resolved.
  • IPv6: (none)
  • IPv4: 216.198.79.1
  • Trying 216.198.79.1:443…
  • connect to 216.198.79.1 port 443 from 192.168.0.4 port 58214 failed: Operation timed out
  • Failed to connect to bolaoless.com port 443 after 75003 ms: Couldn’t connect to server
  • Closing connection
    └───────────────────────────────────────
2

Hi Rcaram,

Since the domain is resolving to 216.198.79.1 but the TCP connection to port 443 is timing out, I’d separate DNS resolution from network reachability.

The DNS lookup itself appears to be working. The failure is happening after that, when your network tries to connect to the Vercel edge IP. That makes this look less like a Next.js/app issue and more like either a regional ISP route issue, stale local resolver cache, or an apex-domain-specific DNS/routing problem.

A few useful checks while the issue is happening:

dig A bolaoless.com +short
dig CNAME www.bolaoless.com +short
dig NS bolaoless.com +short
curl -Iv https://bolaoless.com
traceroute 216.198.79.1

I’d also test the same URL from mobile data, another ISP, and a VPN. If it works through VPN/mobile but times out only on your normal Brazilian network, that strongly points to a regional routing/reachability issue rather than the domain being misconfigured.

If the subdomains work, compare their DNS records with the apex domain too. They may be reaching Vercel through a different record path.

Can you share the outputs of the dig commands and whether the site works from mobile data or VPN?