Differences

This shows you the differences between two versions of the page.

--- useful:dns [2024/12/30 18:19] – created admin
+++ useful:dns [2025/02/17 16:56] (current) – admin
@@ Line 1: / Line 1: @@
+[[useful:contents|Contents Page]]
+====== DNS Policies ======
-ns1 atlanta, GA
+  * ns1 Atlanta, GA
-ns2 hanover, NJ
+  * ns2 Hanover, NJ
-ns3 richardson, TX
+  * ns3 Richardson, TX
-ns4 freemont, CA
+  * ns4 Freemont, CA
-ns5 london, UK
+  * ns5 London, UK
-ns6 frankfurt
+  * ns6 UK (mine - dedicated DNS)
-ns7 bengaluru
+  * ns7 Bengaluru (mine, also Kuma)
-optimum for us coverage ns1,ns4
-Yes, selecting based on target areas makes sense. Here's how I'd approach it based on different scenarios:
+==== US-focused operations ====
+  * ns4 (Fremont) - West Coast
+  * ns1 (Atlanta) - East Coast
-US-focused operations:
-- ns4 (Fremont) - West Coast
-- ns1 (Atlanta) - East Coast
 Perfect 2-server minimum setup for US coverage
-US + Europe operations:
+==== US + Europe operations ====
-- ns4 (Fremont) - West Coast US
-- ns1 (Atlanta) - East Coast US
+  * ns4 (Fremont) - West Coast US
-- ns6 (Frankfurt) - Central Europe
+  * ns1 (Atlanta) - East Coast US
+  * ns6 (Frankfurt) - Central Europe
 Good 3-server setup covering both continents
-Global operations:
+==== Global operations ====
-- ns4 (Fremont) - West Coast US & Pacific
-- ns1 (Atlanta) - East Coast US
+  * ns4 (Fremont) - West Coast US & Pacific
-- ns6 (Frankfurt) - Europe
+  * ns1 (Atlanta) - East Coast US
-- ns7 (Bengaluru) - Asia/India
+  * ns6 (UK) - UK
+  * ns7 (Bengaluru) - Asia/India
 Optimal 4-server setup for global coverage
 The other servers (Hanover, Richardson, London) become less critical because:
-- Hanover overlaps with Atlanta
-- Richardson overlaps with both US coasts
+  * Hanover overlaps with Atlanta
-- London is less optimal than Frankfurt for Europe
+  * Richardson overlaps with both US coasts
+  * London is less optimal than Frankfurt for Europe
 This approach maximizes coverage while keeping the nameserver count manageable.