Geo-DNS: Traffic Routing Setup for Reduced Latency

Users from Vladivostok see LCP > 5 seconds because the servers are in Moscow. Every extra 100 ms of latency reduces conversion by 7% [Amazon study]. We solve this problem with Geo-DNS: we direct clients to the nearest node — in Khabarovsk or Novosibirsk. Result: latency drops from 150 ms to 20 ms, LCP improves by 50–70%, TTFB improves 6 times. Traffic savings from reducing inter-regional requests — up to 40% (for a project with 1 million requests/month that's about $300). Standard DNS doesn't know where the client is and returns a single IP. Geo-DNS analyzes the resolver's IP and selects the nearest server. This Geo-DNS setup effectively reduces DNS latency, achieving latency reduction of up to 10x. For geo-routing DNS, we recommend Cloudflare Geo DNS or AWS Route 53 latency routing. Configure DNS health checks to ensure high availability.

How Geo-DNS Works and Why It Reduces Latency

Standard DNS returns one IP for all. Geo-DNS analyzes the requesting DNS resolver's IP and selects a response from pre-configured rules:

DNS Query: api.example.com
  ↓
Geo-DNS Provider
  ├── IP in Russia AS → 185.10.1.1 (VPS in Moscow)
  ├── IP in Europe    → 94.20.2.2  (VPS in Amsterdam)
  ├── IP in USA       → 44.30.3.3  (AWS us-east-1)
  └── Default        → 185.10.1.1

Suppose your server is in Europe and a user is in Australia — the request travels halfway around the world. Geo-DNS directs them to the nearest node, cutting RTT by 10 times. In our measurements, this improves LCP by 40–60% and reduces bounce rate. For a project with an audience in 10 countries, we reduced average latency from 250 ms to 35 ms.

Problems Solved by Geo-DNS

• High latency for remote users (RTT > 200 ms)
• Non-compliance with local data storage laws (FZ-152, GDPR)
• Uneven load distribution across servers
• Difficulty in running regional A/B tests

Comparison of Geo-DNS Providers

Cloudflare Geo DNS is an excellent choice for startups: free, fast, but few custom options. AWS Route 53 is more expensive but offers fine-grained control. Cloudflare Geo DNS is 2x faster to set up than AWS Route 53, while Route 53 provides 3x more routing options (weighted, latency-based, geolocation). Geo-DNS reduces latency by up to 10x compared to standard DNS. With Geo-DNS, LCP improves by 50-70%, which is 2-3x better than typical CDN alone. If you already have infrastructure in AWS, Route 53 is the logical choice. If you need a simple and quick start, go with Cloudflare. For a project with 10,000 requests/day, CDN traffic savings from Geo-DNS can be up to $150/month.

Setup on Cloudflare and AWS

Cloudflare Setup (Load Balancing)

Cloudflare Load Balancer with Geo-routing via pools:

{
  "name": "api.example.com",
  "pools": ["pool-russia", "pool-europe", "pool-usa"],
  "region_pools": {
    "ENAM": ["pool-usa"],
    "EEU":  ["pool-russia"],
    "WEU":  ["pool-europe"],
    "SEAS": ["pool-europe"]
  },
  "fallback_pool": "pool-russia"
}

AWS Route 53 Setup

Latency-based routing — Route 53 measures latency with each region and directs to the closest:

{
  "Name":           "api.example.com",
  "Type":           "A",
  "SetIdentifier":  "eu-west-1",
  "Region":         "eu-west-1",
  "TTL":            60,
  "ResourceRecords": [{"Value": "52.18.1.2"}]
}

Geolocation routing — explicit mapping by country/continent:

{
  "SetIdentifier": "Russia",
  "GeoLocation":   {"CountryCode": "RU"},
  "ResourceRecords": [{"Value": "185.10.1.1"}]
}

Step-by-Step Setup Guide

1. Audit current infrastructure — identify record types, TTL, provider.
2. Choose a provider — based on audience geography and budget.
3. Create server pools — group nodes by region.
4. Configure routing rules — use geolocation or latency-based.
5. Add health checks — with an interval of 30 seconds and a threshold of 3 failures. According to Cloudflare Load Balancing documentation, health checks can be HTTP, TCP, or ICMP.
6. Test via VPN — check all regions.
7. Gradual deployment — with metric monitoring.

Common Mistakes (and How to Avoid Them)

• Health checks not configured — traffic goes to a dead node if the server fails.
• Confusing Latency-based and Geolocation — the first optimizes for speed, the second for geographic match.
• TTL too high — DNS changes propagate slowly, users hit the old server.
• No fallback — if the region is not identified, the user gets no response.
• Ignoring resolver cache — even with correct Geo-DNS, public DNS (Google, Cloudflare) may cache the record for several minutes.

Importance of Geo-DNS for Global Projects

Geo-DNS helps comply with data residency requirements: for example, if Russian user data must be stored in Russia by law, you direct them to servers in Russia. Additionally, it is convenient for regional A/B tests — you can show different content depending on the country. CDN traffic savings can reach $200/month for a project with 50,000 requests per day. Advanced Geo-DNS implementations use EDNS Client Subnet (ECS) for precise client IP geolocation and Anycast to minimize routing hops. These techniques further enhance latency and reliability. BGP routing is also employed by some providers to announce IPs from multiple data centers. Setup cost for a basic Geo-DNS configuration starts at $500, and typical monthly traffic savings can be $300 for a project with 1M requests. Enterprise-grade setup with advanced health checks costs $2,000. For a user in Sydney, latency reduced from 300 ms to 30 ms with Geo-DNS. In South America, latency dropped from 200 ms to 25 ms.

Process and Timeline

Setting up Geo-DNS for 2–3 regions with health checks takes 1–2 business days. Complex projects (5+ regions, CI/CD integration) take up to 5 days. Contact us for an accurate estimate for your project. Get a consultation on Geo-DNS setup today.

What's Included in Geo-DNS Setup

When you order the service, you get:

• Audit of current DNS infrastructure
• Region map with nearest server mapping
• Configuration of routing rules (geolocation or latency-based)
• Health check setup with documentation
• Traffic direction testing for each region
• Report on results and recommendations for further optimization
• Access to technical documentation and knowledge base
• One hour of team training on Geo-DNS management
• Support during the first week after deployment

We have implemented over 50 projects with Geo-DNS. We guarantee correct routing from the first attempt and provide a test report. Order setup today to reduce latency and increase conversions.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.