Domain Registration and DNS Management

Domain Registration Flow 💰

Transaction Process

When purchasing a domain:

1. Payment to registrar (e.g., GoDaddy, $15/year)
2. Registrar commission - Registrar retains portion as profit
3. ICANN submission - Registrar contacts ICANN on your behalf, submits registration forms
4. ICANN registration fee - Portion of payment goes to ICANN
5. Domain authority granted - ICANN officially records domain ownership

Domain Ownership Considerations 🚨

Privacy Protection Services

Without privacy protection:

• ICANN records you as owner
• Full control over domain
• Easy registrar transfers

With privacy protection:

• Registrar listed as owner with ICANN
• Your identity hidden (privacy benefit)
• Registrar legally owns domain (control risk)

Potential issues:

• Difficult registrar transfers
• Vendor lock-in
• Renewal fee increases
• Limited control over your domain

Recommendation: Understand ownership implications before purchasing privacy protection services.

Country-Specific TLD Requirements

Example: .in domains (India)

• Controlled by Indian government
• Requires government approval
• Identity verification required (Aadhaar or PAN card)
• Portion of fees goes to government

Pattern applies to all country-code TLDs:

• .cn → Chinese government
• .uk → UK government
• .de → German government
• Each has specific requirements and governance

---

DNS Record Management 🔧

DNS Configuration Interface

Access: Domain registrar dashboard (Namecheap, GoDaddy, etc.)

• Basic DNS tab: Default configurations
• Advanced DNS tab: Full record management

A Records (Address Records)

Function: Map domain name to IP address

Example:

Configuration: Modifiable through registrar dashboard

Default Behavior

When no IP assigned:

• Registrar assigns default IP pointing to their servers
• Displays "parked domain" placeholder
• Reconfigurable once infrastructure ready

Advanced DNS Routing

Capabilities beyond IP mapping:

• URL redirects (e.g., domain → LinkedIn profile)
• Path-based routing
• Conditional traffic routing
• Complex traffic flow control

Use cases: DNS records control traffic flow, not just static IP mapping.

---

Domain Availability Checking 🌐

Registrar Availability Lookups

Question: How do registrars quickly determine domain availability?

Answer: They use imperfect caching systems.

Implementation:

• Registrars cache domain availability data
• Cache is not real-time or perfectly accurate
• No public database of all available domains

Common user experience:

1. Search shows domain as "available"
2. Add to cart
3. Checkout reveals domain actually taken

Reality: "Instant" availability checks are cached approximations, not authoritative lookups.

Key insight: Internet infrastructure relies heavily on caching with accepted imperfection trade-offs.

ICANN and Internet Governance 🌐

Historical Context

Origin:

• DARPA (US Defense Department) invented internet
• Made public by US government
• ICANN established as governing body
• US-based infrastructure and governance

Current state: ICANN maintains de facto authority over global domain system due to internet's US origins and widespread adoption.

Alternative Networks

Technically possible: Anyone can build independent internet infrastructure

Adoption challenge: Network effects favor established systems

Example: China's Internet

• Operates separate DNS infrastructure
• Chinese government controls domains
• Different governance rules
• Great Firewall enforces separation
• Some infrastructure shared, governance separate

Result: Multiple "internets" with different governance models coexist.

---

Domain Registrar Business Model 💼

Market characteristics:

• Razor-thin margins
• Intense competition
• Commoditized service

Historical success: Early movers (1990s) built significant wealth

Current state: Highly competitive, pressure on business practices

GeoDNS Reality and Alternatives 🗺️

GeoDNS Adoption Status

Question: Does GeoDNS add processing overhead? Would returning all load balancer IPs be more efficient?

Answer: GeoDNS has limited real-world adoption despite theoretical benefits.

Reality:

• Most DNS providers do not implement GeoDNS
• Insufficient market penetration
• Alternative approaches more common

Alternative: Anycast

• Routing protocol-level solution
• Network layer geographic routing
• More widely deployed than DNS-based geolocation

GeoDNS Performance (When Implemented)

Efficient implementation:

• Pre-compute IP → Geolocation mapping
• Store in HashMap
• O(1) lookup during query
• Not computationally expensive

Why low adoption despite efficiency: Technical performance doesn't guarantee ecosystem adoption.

---

DNS Query and Propagation 🔄

DNS Hierarchy and Synchronization

New domain registration flow:

1. Domain purchased via registrar (e.g., GoDaddy)
2. Registrar submits to ICANN
3. Root DNS servers periodically sync with ICANN
4. Lower-tier DNS servers sync with root servers
5. Data propagates down hierarchy

User DNS query flow:

• Clients query local DNS server (cached data)
• NOT direct ICANN queries
• Data from periodic synchronization

Recursive DNS Queries

When local DNS lacks data:

• Recursive query up hierarchy
• Local DNS → Parent DNS → Root DNS → ICANN
• Expensive operation

Optimization:

• DNS servers cache aggressively
• Minimize recursive queries
• Trade-off: Speed vs freshness

DNS update propagation:

• Changes not instant
• 4-5 minutes typical (depends on TTL)
• Cached data expires based on TTL settings
• Fresh data obtained via recursive query when needed

---

Key Takeaways 💡

1. Domain ownership requires careful consideration.
2. DNS configuration is powerful beyond simple IP mapping.
3. Internet governance is US-centric but not universal.