Hacker News Reader

I was surprised by that too: typically I’ve only seen such high latency on Netlify based sites which exclusively uses aws-east for the whole world.

View on HN

This is not accurate. I do not know the details but netlify served things from a CDN by default if you set things up correctly with a CNAME entry in your DNS record.

People often misconfigure things by pointing their domain to netlify's IP with an A entry, but this is a user problem, not a netlify problem.

I'm sure their builds/functions run in a single region but not static files

The Netlify docs are quite bad so I can see this happening. Also, the Netlify Functions ate locked to one AWS region too.

Based on my limited knowledge, you have to point your root domain (e.g. example.com) to their IP address because it’s an A record.

For the a CNAME record (e.g. wwww) it can be pointed to their CDN.

I think if you use Netlify DNS for your domain, then you can point A records to their CDN because it’s an alias at that point. Like, A record aliases on AWS Route53.

I found all of Netlify particularly confusing and honestly a bit scary. Now I’m on CF and it couldn’t be simpler.

Reply on news.ycombinator.com