---
title: 'DNS Policies'
url: 'https://manuals.remository.com/useful/dns-policies'
markdown: 'https://manuals.remository.com/useful/dns-policies.md'
date: '2026-10-06'
description: 'DNS Policies ns1 Atlanta, GA ns2 Hanover, NJ ns3 Richardson, TX ns4 Freemont, CA ns5 London, UK ns6 UK (mine - dedicated DNS) US-focused operations ns4 (Fremont) - West Coast ns1 (Atlanta) - East Coast Perfect 2-server minimum setup for US coverage US + Europe operations ns4 (Fremont) - West C…'
---

[](#) [ edit this page](https://github.com/getgrav/grav-skeleton-rtfm-site/blob/develop/pages/06.dns-policies/chapter.md) 

# DNS Policies

1. ns1 Atlanta, GA
2. ns2 Hanover, NJ
3. ns3 Richardson, TX
4. ns4 Freemont, CA
5. ns5 London, UK
6. ns6 UK (mine - dedicated DNS)

### US-focused operations

1. ns4 (Fremont) - West Coast
2. ns1 (Atlanta) - East Coast

Perfect 2-server minimum setup for US coverage

### US + Europe operations

1. ns4 (Fremont) - West Coast US
2. ns1 (Atlanta) - East Coast US
3. ns6 (Frankfurt) - Central Europe

Good 3-server setup covering both continents

### Global operations

1. ns4 (Fremont) - West Coast US & Pacific
2. ns1 (Atlanta) - East Coast US
3. ns6 (UK) - UK

Optimal 3-server setup for global coverage

The other servers (Hanover, Richardson, London) become less critical because:

1. Hanover overlaps with Atlanta
2. Richardson overlaps with both US coasts
3. London is less optimal than Frankfurt for Europe

This approach maximizes coverage while keeping the nameserver count manageable.

---

## Navigation

- Previous: [Mikrotik and Ubiquiti](https://manuals.remository.com/useful/mikrotik-and-ubiquiti.md)
- Next: [Word Processing](https://manuals.remository.com/useful/word-processing.md)