Geo-DNS: Geographic DNS Routing with Cloudflare, AWS, Nginx

Introduction

Imagine: your site is hosted in Europe, and users from Australia complain about slowness. While the DNS resolver returns an IP, 200 ms pass — this can be reduced to 50 ms with Geo-DNS (geographic routing). We have been configuring geographic and latency-based routing for years for projects ranging from startups to enterprise. Our engineers are Cloudflare and AWS certified, guaranteeing quality implementation. In this article — practical configurations for Cloudflare, AWS Route53, and Nginx GeoIP used in production. The setup pays for itself within 3–6 months by reducing TTFB by 40–60%, and savings on DNS traffic and CDN can reach hundreds of dollars per month. Get a consultation from a Geo-DNS engineer — we will evaluate your project.

Problems that Geo-DNS solves

Without Geo-DNS, users experience high latency — DNS queries travel to the parent DNS thousands of kilometers away, causing TTFB over 500 ms for remote regions, reducing conversion by 20%. Traffic is unevenly distributed to a single server, creating unnecessary load. When a data center in a region fails, users are left without service due to lack of failover. Geo-DNS addresses all this at the DNS resolution level, before the TCP connection is established.

Comparison of Geo-DNS providers

Cloudflare Load Balancing is 2x faster to configure than a custom Nginx setup, and TTFB is reduced by 50%.

How to choose between Cloudflare and AWS Route53?

Cloudflare Load Balancing is easier to set up and includes built-in monitoring. It is suitable for quick starts and small projects. AWS Route53 offers more flexibility with latency-based routing, allowing routing based on actual latency rather than geography. This is especially useful with heterogeneous network infrastructure. If you need full control, choose Nginx with GeoIP2, but manual updates of the MaxMind database are required.

Configuring Cloudflare Load Balancing (Geo-steering)

Cloudflare offers geo-steering out of the box. You specify pools for regions (e.g., ENAM — East Coast US, WEU — Western Europe), and the load balancer automatically directs traffic. Example configuration via API:

curl -X POST "https://api.cloudflare.com/client/v4/zones/{zone_id}/load_balancers" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  --data '{
    "name": "api.mysite.com",
    "fallback_pool": "us-east-1-pool",
    "default_pools": ["us-east-1-pool"],
    "region_pools": {
      "ENAM": ["us-east-1-pool"],
      "WNAM": ["us-west-2-pool"],
      "EEU":  ["eu-central-1-pool"],
      "WEU":  ["eu-west-1-pool"],
      "SEAS": ["ap-southeast-1-pool"],
      "NEAS": ["ap-northeast-1-pool"]
    },
    "steering_policy": "geo",
    "session_affinity": "ip_cookie",
    "session_affinity_ttl": 300
  }'

Cloudflare documentation recommends using session affinity to maintain user sessions.

Configuring AWS Route53

Geolocation Routing

For precise routing by country or continent, use geolocation records. Example Terraform:

resource "aws_route53_record" "api_eu" {
  zone_id = var.zone_id
  name    = "api.mysite.com"
  type    = "A"
  set_identifier = "eu-users"
  geolocation_routing_policy {
    continent = "EU"
  }
  alias {
    name                   = aws_lb.eu_west_1.dns_name
    zone_id                = aws_lb.eu_west_1.zone_id
    evaluate_target_health = true
  }
}

resource "aws_route53_record" "api_default" {
  zone_id = var.zone_id
  name    = "api.mysite.com"
  type    = "A"
  set_identifier = "default"
  geolocation_routing_policy {
    country = "*"
  }
  alias {
    name                   = aws_lb.us_east_1.dns_name
    zone_id                = aws_lb.us_east_1.zone_id
    evaluate_target_health = true
  }
}

Why latency-based routing is better?

Latency-based routing considers not geographic distance but network latency — traffic from Europe might be faster to a data center in Virginia than in Frankfurt if backbones are congested. AWS automatically selects the fastest region. This approach gives more accurate distribution, especially for mobile users.

Example configuration:

resource "aws_route53_record" "api_latency_eu" {
  zone_id = var.zone_id
  name    = "api.mysite.com"
  type    = "A"
  set_identifier = "eu-west-1"
  latency_routing_policy {
    region = "eu-west-1"
  }
  alias {
    name                   = aws_lb.eu.dns_name
    zone_id                = aws_lb.eu.zone_id
    evaluate_target_health = true
  }
}

Configuring Nginx with GeoIP2

If you want full control over routing, use Nginx with the geoip2 module and MaxMind GeoLite2 database. It is free and flexible.

Nginx configuration

Install the module and download the database (updated monthly). Then configure country mapping to backends:

load_module modules/ngx_http_geoip2_module.so;

http {
  geoip2 /etc/nginx/geoip/GeoLite2-Country.mmdb {
    $geoip2_country_code country iso_code;
    $geoip2_country_name country names en;
  }

  map $geoip2_country_code $backend {
    default        http://us-backend:3000;
    RU             http://ru-backend:3000;
    UA             http://eu-backend:3000;
    "~^(DE|AT|CH)" http://eu-backend:3000;
    "~^(GB|IE|FR)" http://eu-backend:3000;
  }

  server {
    listen 80;
    location / {
      proxy_pass $backend;
      proxy_set_header X-Country-Code $geoip2_country_code;
      proxy_set_header X-Real-IP $remote_addr;
    }
  }
}

You can also implement automatic redirect to a language version based on GeoIP.

TTL and DNS caching

Cloudflare Load Balancing automatically reduces TTL during health check failover.

How Geo-DNS affects TTFB and Core Web Vitals?

Initial DNS latency directly impacts TTFB, which is a Core Web Vitals metric. Geo-DNS reduces TTFB by 40–60%, improving LCP and overall user experience. Google considers TTFB in ranking, so implementing Geo-DNS can indirectly boost search positions. This is especially important for sites with a global audience — a 100 ms reduction in TTFB can increase conversion by 5%.

Process for setting up Geo-DNS

We take a systematic approach:

1. Audit the current DNS zone, analyze user geography (from Nginx logs or CDN).
2. Design — select provider, pool scheme, TTL.
3. Implementation — configure DNS via Terraform or Cloudflare API, set up health checks.
4. Testing — verify from different points (via VPN, AWS Lightsail in various regions, dig from public DNS).
5. Monitoring — set up alerts for latency changes or failures.

What is included in the result

• A working Geo-DNS scheme with documentation.
• Access to all providers (Cloudflare, AWS, control panel).
• Team training: how to add new regions, change TTL.
• Support for 14 days after implementation.

Our engineers hold Cloudflare and AWS certifications and have completed 50+ content delivery optimization projects. The setup pays for itself in 3–6 months by reducing TTFB by 40–60% and decreasing CDN traffic.

How to test Geo-DNS

Use dig with a specific resolver:

dig @8.8.8.8 api.mysite.com       # USA
dig @1.1.1.1 api.mysite.com       # Europe
dig @77.88.8.8 api.mysite.com     # Russia

If routing is configured correctly, the responses will differ in IP addresses.

Get a consultation on Geo-DNS — our engineers will help you choose the optimal routing scheme. Order an audit of your current DNS setup and find out how much you can save.

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.