When you create a subdomain on localnode.app, we provision the DNS record directly through the Cloudflare API. That means your subdomain inherits the full weight of Cloudflare's infrastructure - and it's worth understanding why that matters.
What anycast means
Traditional DNS has one authoritative server you query, wherever it is in the world. Anycast is different: the same IP address is advertised from hundreds of locations simultaneously. When your browser queries Cloudflare's DNS for your subdomain, it automatically connects to the nearest Cloudflare data centre - not one across the ocean.
Cloudflare operates over 300 data centres globally. A query from Sydney hits a Sydney node. A query from Frankfurt hits a Frankfurt node. The round-trip time for DNS resolution drops from hundreds of milliseconds to single digits.
What this means for localnode.app subdomains
Every subdomain you create resolves fast regardless of where the visitor is. The DNS layer is handled; what determines end-to-end speed after that is where your server is, which is your concern. But at least the DNS step isn't the bottleneck.
The proxy option
If you enable Cloudflare proxying on a subdomain (available on advanced DNS), your traffic also passes through Cloudflare's edge. You get DDoS mitigation, caching, and your real server IP is hidden. For anything public-facing, it's worth considering.