Hello.
My Netlify subdomain works correctly, but my custom .ru domain does not.
Site name:
sultan-kozhevnik
Custom domain:
sultan-kozhevnik dot ru
Framework:
Next.js App Router
Problem:
HTML is returned by Netlify, SSL works, but static assets under /_next/static/ start downloading and then stall around 21 KB.
DNS:
NS: ns1.reg.ru, ns2.reg.ru
A apex: 75.2.60.5
CNAME www: sultan-kozhevnik dot netlify dot app
No AAAA record on apex.
DNS checks:
8.8.8.8 and 1.1.1.1 both return 75.2.60.5.
NS records return ns1.reg.ru / ns2.reg.ru.
curl -I custom domain result:
HTTP/1.1 200 OK
Server: Netlify
X-Powered-By: Next.js
X-Nf-Request-Id: 01KQWTEXCZ68GVY4VZ0ZJAEZW3
Static asset download result through custom domain:
77 27778 77 21480
Same asset through Netlify subdomain:
100 27778
I also tested with --resolve to 75.2.60.5 and the custom domain still stalls:
77 27778 77 21485
DNS cache and browser cache were cleared.
I already triggered “Deploy project without cache”.
Could this be an edge/CDN routing issue for the custom domain?
Can someone check or re-check the edge configuration for this custom domain?
Request IDs:
01KQWTEXCZ68GVY4VZ0ZJAEZW3
01KQWTF42KRWGSG96QATQ038JN
01KQWTGCMB6C7FPAEHRCJVT4K1
Thank you.
Update from registrar:
REG RU checked the domain and confirmed:
NS:
ns2,reg,ru
A:
75.2.60.5
Reverse DNS:
acd89244c803f7181.awsglobalaccelerator.com
They confirmed there are no residual DNS records and no visible issue from their side.
I also created a completely clean Next.js App Router test project and temporarily moved the same custom domain to it. The issue still happens on the clean test project: static assets fail with ERR_CONNECTION_CLOSED / curl stalls around 18–21 KB.
So this seems to follow the custom domain / Netlify edge route, not my original project.
Update:
I re-checked WebPageTest more carefully.
The page is not actually loaded correctly from WebPageTest either.
Location:
Bratislava - Chrome
Result:
The page renders as mostly unstyled HTML / broken Next.js starter page.
CSS/JS/static assets are not loaded correctly.
So the issue is not only local to my ISP or my PC.
It also reproduces from an external WebPageTest location.
Important:
I also created a completely clean Next.js App Router project and moved the same custom domain to it.
The clean test project has the same issue with the custom domain.
The Netlify subdomain for the same test project works correctly.
The custom .ru domain does not.
This seems to confirm that the problem follows the custom domain / Netlify edge routing, not my project code.
Update:
I deployed the same clean Next.js test project to a separate VPS with Nginx.
I added a test subdomain:
test.sultan-kozhevnik dot ru → VPS IP
Testing the VPS directly with --resolve works correctly:
curl.exe -L --http1.1 --resolve test.sultan-kozhevnik.ru:80:80.93.52.150 test,sultan-kozhevnik,ru -o NUL
Result:
100 12117 100 12117
So the same domain zone works correctly through a regular VPS + Nginx setup.
The issue only appears when the custom domain is served through Netlify custom domain/CDN.