How to Configure DNS

Last Updated: October 24, 2025

DNS (Domain Name System) is the foundation of your online presence, translating domain names into IP addresses. This comprehensive guide walks you through DNS configuration, from basic setup to advanced techniques, ensuring your domain works flawlessly.

Understanding DNS Basics

What is DNS?

DNS Explained Simply:

DNS is like the internet's phonebook. When you type example.com, DNS translates it to an IP address like 192.0.2.1 that computers understand.

The Translation Process:

User types: www.example.com
↓
DNS looks up: "Where is www.example.com?"
↓
DNS responds: "It's at 192.0.2.1"
↓
Browser connects to: 192.0.2.1
↓
Website loads

Why DNS Configuration Matters

Critical for:

• 🌐 Website Access - Visitors find your site
• 📧 Email Delivery - Messages reach inboxes
• 🔒 Security - SPF, DKIM, DMARC protection
• ⚡ Performance - Fast resolution speeds
• 🛡️ Protection - Prevent hijacking and downtime

DNS Components

Key Terms You Need to Know:

Domain Name

Your website address: example.com

DNS Records

Instructions that tell DNS where to route traffic

Nameservers

Servers that store and provide your DNS records

• Example: ns1.pupam.com, ns2.pupam.com

TTL (Time to Live)

How long DNS information is cached (in seconds)

• Low TTL (300s): Fast updates, more queries
• High TTL (86400s): Fewer queries, slower updates

DNS Propagation

Time for DNS changes to spread globally (5 minutes to 48 hours)

Common DNS Record Types

A Record (Address Record)

Purpose: Points domain to IPv4 address

When to Use:

• Connect domain to web server
• Point subdomain to specific server
• Direct traffic to IP address

Format:

Type: A
Host: @ (or subdomain)
Value: 192.0.2.1
TTL: 3600

Examples:

@ → 192.0.2.1 (example.com)
www → 192.0.2.1 (www.example.com)
shop → 192.0.2.2 (shop.example.com)

Common Uses:

• Main website: example.com → 192.0.2.1
• WWW subdomain: www.example.com → 192.0.2.1
• App subdomain: app.example.com → 192.0.2.5

AAAA Record (IPv6 Address)

Purpose: Points domain to IPv6 address

Format:

Type: AAAA
Host: @
Value: 2001:0db8:85a3::8a2e:0370:7334
TTL: 3600

When Needed:

• Modern infrastructure
• IPv6-only networks
• Future-proofing
• Performance optimization

Best Practice: Add both A and AAAA records

CNAME Record (Canonical Name)

Purpose: Points domain to another domain (alias)

Format:

Type: CNAME
Host: www
Value: example.com
TTL: 3600

Common Uses:

• WWW redirect: www → example.com
• CDN setup: cdn → cdn-provider.com
• Service aliasing: mail → mailserver.provider.com

Important Restrictions:

• ❌ Cannot be used for root domain (@)
• ❌ Cannot coexist with other records on same name
• ✅ Must point to domain name, not IP

Examples:

www → example.com
blog → blogplatform.com
shop → shopify.myshopify.com

MX Record (Mail Exchange)

Purpose: Directs email to mail servers

Format:

Type: MX
Host: @
Value: mail.example.com
Priority: 10
TTL: 3600

Priority System:

• Lower number = Higher priority
• Primary server: Priority 10
• Backup server: Priority 20

Complete Email Setup:

Priority 10: mail1.pupam.com (primary)
Priority 20: mail2.pupam.com (backup)
Priority 30: mail3.pupam.com (tertiary)

Why Multiple Records:

• Redundancy if primary fails
• Load distribution
• Better reliability
• Business continuity

TXT Record (Text Record)

Purpose: Stores text information for various purposes

Format:

Type: TXT
Host: @
Value: "v=spf1 include:_spf.pupam.com ~all"
TTL: 3600

Common Uses:

SPF (Sender Policy Framework)

Authorizes mail servers to send email on your behalf

v=spf1 include:_spf.pupam.com ~all

DKIM (DomainKeys Identified Mail)

Cryptographic email authentication

v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA...

DMARC (Domain-based Message Authentication)

Email authentication policy

v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com

Domain Verification

Prove domain ownership for services

google-site-verification=abc123xyz789

Best Practices:

• Keep under 255 characters per string
• Use multiple strings if longer
• Quote values containing spaces
• Validate syntax before adding

NS Record (Nameserver)

Purpose: Delegates domain to nameservers

Format:

Type: NS
Host: @
Value: ns1.pupam.com
TTL: 86400

Standard Setup:

@ → ns1.pupam.com
@ → ns2.pupam.com
@ → ns3.pupam.com
@ → ns4.pupam.com

When to Modify:

• Changing DNS provider
• Using custom nameservers
• Delegating subdomain to different DNS

Warning: Incorrect NS records break everything!

SRV Record (Service Record)

Purpose: Defines location of specific services

Format:

Type: SRV
Service: _service
Protocol: _tcp
Priority: 10
Weight: 5
Port: 5060
Target: server.example.com
TTL: 3600

Common Uses:

• VoIP/SIP services
• XMPP/Jabber chat
• LDAP directory
• Minecraft servers

Example:

_sip._tcp.example.com → sipserver.example.com:5060
_minecraft._tcp.example.com → game.example.com:25565

CAA Record (Certification Authority Authorization)

Purpose: Controls which CAs can issue SSL certificates

Format:

Type: CAA
Host: @
Flags: 0
Tag: issue
Value: letsencrypt.org
TTL: 3600

Security Setup:

0 issue "letsencrypt.org"
0 issuewild "letsencrypt.org"
0 iodef "mailto:security@example.com"

Benefits:

• Prevents unauthorized SSL issuance
• Security best practice
• Required by some CAs
• Protects against mis-issuance

Step-by-Step DNS Configuration

Method 1: Using Our DNS Manager

Access DNS Settings

Step-by-Step:

1. Log into your account

   • Go to manage.pupam.com
   • Sign in with credentials

2. Navigate to Domains

   • Click "Domains" in sidebar
   • Select your domain from list

3. Open DNS Management

   • Click "DNS Settings" or "Manage DNS"
   • You'll see current DNS records

Add New DNS Record

Adding an A Record (Website):

1. Click "Add Record"

   • Select "A Record" from type dropdown

2. Fill in Details:

   Type: A Record
   Host/Name: @ (for root domain)
            or www (for www subdomain)
            or subdomain name
   
   Value/Points to: 192.0.2.1
   (Your server's IP address)
   
   TTL: 3600 (1 hour)
        or 300 (5 minutes) for testing
   

3. Verify Information

   • Double-check IP address
   • Confirm host name
   • Review TTL setting

4. Click "Save" or "Add Record"

   • Record is created
   • Changes begin propagating

Wait Time: 5 minutes to 48 hours (typically 1-2 hours)

Add MX Records (Email)

Email Server Setup:

1. Click "Add Record"

   • Select "MX Record"

2. Primary Mail Server:

   Type: MX Record
   Host: @
   Value: mail1.pupam.com
   Priority: 10
   TTL: 3600
   

3. Click "Add Record" Again

   • Add backup server

4. Backup Mail Server:

   Type: MX Record
   Host: @
   Value: mail2.pupam.com
   Priority: 20
   TTL: 3600
   

5. Save Both Records

Verify Setup:

• Primary (Priority 10) listed first
• Backup (Priority 20) listed second
• Both point to correct mail servers

Add TXT Records (Email Authentication)

SPF Record:

1. Add New TXT Record

   Type: TXT
   Host: @
   Value: v=spf1 include:_spf.pupam.com ~all
   TTL: 3600
   

2. Save Record

DKIM Record:

1. Get DKIM Key

   • From email provider
   • Usually in email settings

2. Add TXT Record

   Type: TXT
   Host: default._domainkey
   Value: v=DKIM1; k=rsa; p=[your-public-key]
   TTL: 3600
   

DMARC Record:

1. Add TXT Record

   Type: TXT
   Host: _dmarc
   Value: v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
   TTL: 3600
   

Edit Existing Records

Modify DNS Record:

1. Find the record in DNS manager
2. Click "Edit" or pencil icon
3. Update values as needed
4. Click "Save"
5. Wait for propagation

Common Edits:

• Changing IP address
• Updating TTL
• Modifying priority
• Correcting typos

Delete Records

Remove DNS Record:

1. Find the record
2. Click "Delete" or trash icon
3. Confirm deletion
4. Record is removed

Warning: Be careful! Deleting wrong records breaks services.

Method 2: Changing Nameservers

When to Change Nameservers:

• Switching DNS providers
• Using external DNS (Cloudflare, AWS Route 53)
• Moving to managed hosting
• Using CDN DNS

At Domain Registrar

Step-by-Step:

1. Log into Domain Registrar

   • Where you bought domain
   • GoDaddy, Namecheap, Google Domains, etc.

2. Find Domain Settings

   • My Domains
   • Domain Management
   • DNS Settings

3. Locate Nameservers Section

   • Usually labeled "Nameservers"
   • May be under "Advanced DNS"

4. Change Nameserver Type

   • Select "Custom Nameservers"
   • Or "Use custom name servers"

5. Enter New Nameservers

   Nameserver 1: ns1.pupam.com
   Nameserver 2: ns2.pupam.com
   Nameserver 3: ns3.pupam.com
   Nameserver 4: ns4.pupam.com
   

6. Save Changes

   • Click "Save" or "Update"
   • May require confirmation

Propagation Time: 24-48 hours (typically 4-8 hours)

Important Notes:

• Keep old records until propagation complete
• Email may be affected during transition
• Website might have brief downtime
• Plan changes during low-traffic periods

Our Nameservers

PUPAM DNS Nameservers:

Primary: ns1.pupam.com
Secondary: ns2.pupam.com
Tertiary: ns3.pupam.com
Quaternary: ns4.pupam.com

Or IP Addresses (if required):

ns1.pupam.com → 192.0.2.1
ns2.pupam.com → 192.0.2.2
ns3.pupam.com → 192.0.2.3
ns4.pupam.com → 192.0.2.4

Common DNS Configurations

Basic Website Setup

Minimal Configuration:

Required Records:

Type: A
Host: @
Value: 192.0.2.1
TTL: 3600

Type: A (or CNAME)
Host: www
Value: 192.0.2.1 (or example.com for CNAME)
TTL: 3600

Result:

• example.com → Your website
• www.example.com → Your website

Website + Email Configuration

Complete Setup:

Website Records:

A Record:
@ → 192.0.2.1

CNAME Record:
www → example.com

Email Records:

MX Records:
Priority 10 → mail1.pupam.com
Priority 20 → mail2.pupam.com

TXT Record (SPF):
@ → "v=spf1 include:_spf.pupam.com ~all"

TXT Record (DKIM):
default._domainkey → "v=DKIM1; k=rsa; p=..."

TXT Record (DMARC):
_dmarc → "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

Result:

• Website works at both root and www
• Email delivered and authenticated
• Protected against spam/spoofing

Subdomain Setup

Create Subdomain:

Option 1: Point to Different Server

Type: A
Host: blog
Value: 192.0.2.5
TTL: 3600

Result: blog.example.com → Different server

Option 2: Alias to Another Domain

Type: CNAME
Host: shop
Value: mystore.shopify.com
TTL: 3600

Result: shop.example.com → Shopify store

Option 3: Point to Same Server

Type: A
Host: app
Value: 192.0.2.1
TTL: 3600

Result: app.example.com → Same server as main site

CDN Configuration

Using CDN (e.g., Cloudflare, CloudFront):

Method 1: CNAME to CDN

Type: CNAME
Host: www
Value: your-domain.cdn-provider.com
TTL: 300

Type: CNAME
Host: cdn
Value: assets.cdn-provider.com
TTL: 3600

Method 2: Change Nameservers

• Point domain to CDN nameservers
• Manage all DNS at CDN provider
• CDN handles all routing

Benefits:

• Faster content delivery
• DDoS protection
• SSL/TLS management
• Caching and optimization

Email-Only Domain

No Website, Just Email:

Email Records:

MX Records:
Priority 10 → mail1.pupam.com
Priority 20 → mail2.pupam.com

TXT (SPF):
@ → "v=spf1 include:_spf.pupam.com ~all"

TXT (DKIM):
default._domainkey → "v=DKIM1; k=rsa; p=..."

TXT (DMARC):
_dmarc → "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

Optional - Redirect to Main Site:

A Record:
@ → 192.0.2.1 (your main website)

CNAME:
www → maindomain.com

Advanced DNS Configuration

DNS Failover Setup

Automatic Failover:

Primary Server:

Type: A
Host: @
Value: 192.0.2.1
TTL: 300 (low TTL for fast switching)

Health Monitoring:

• Monitor primary server
• Switch to backup if down
• Automatic DNS update

Backup Server:

Type: A
Host: @
Value: 192.0.2.2
TTL: 300

Requires:

• DNS provider with health checks
• Multiple servers/IPs
• Monitoring service

Providers Offering This:

• AWS Route 53
• Cloudflare
• DNS Made Easy
• NS1

Load Balancing with DNS

Round-Robin DNS:

Multiple A Records:

Type: A
Host: @
Value: 192.0.2.1
TTL: 300

Type: A
Host: @
Value: 192.0.2.2
TTL: 300

Type: A
Host: @
Value: 192.0.2.3
TTL: 300

How It Works:

• DNS rotates through IPs
• Distributes traffic
• Simple load distribution
• No smart health checks

Limitations:

• Not true load balancing
• Can't detect server failure
• Uneven distribution possible
• Use proper load balancer for production

Geographic DNS Routing

Route Users by Location:

Geo-Routing Setup:

US Traffic → 192.0.2.1 (US server)
EU Traffic → 192.0.2.2 (EU server)
Asia Traffic → 192.0.2.3 (Asia server)

Benefits:

• Lower latency
• Faster performance
• Regional compliance
• Better user experience

Requires:

• Advanced DNS provider
• Servers in multiple regions
• Geographic routing support

Providers:

• AWS Route 53
• Cloudflare
• Azure DNS
• Google Cloud DNS

Custom Email Routing

Department-Specific Email:

MX Records by Subdomain:

Type: MX
Host: @
Value: mail.pupam.com
Priority: 10
(Main company email)

Type: MX
Host: support
Value: support-mail.zendesk.com
Priority: 10
(Support tickets)

Type: MX
Host: marketing
Value: inbound.mailgun.org
Priority: 10
(Marketing emails)

Result:

• user@example.com → Main mail server
• tickets@support.example.com → Zendesk
• campaign@marketing.example.com → Mailgun

Dynamic DNS (DDNS)

For Changing IP Addresses:

Use Cases:

• Home servers
• Dynamic ISP IPs
• Mobile applications
• Testing environments

How It Works:

1. Your device IP changes
2. Device notifies DNS provider
3. DNS record automatically updates
4. Domain points to new IP

Setup:

• Use DDNS-compatible DNS provider
• Install DDNS client on device
• Configure auto-update
• Set low TTL (60-300 seconds)

Providers:

• No-IP
• DynDNS
• Cloudflare (via API)
• Duck DNS

DNS Troubleshooting

Check DNS Propagation

Tools to Check Status:

Online Tools:

• whatsmydns.net - Check globally
• dnschecker.org - Multiple locations
• DNS Propagation Checker - Visual map

How to Use:

1. Enter your domain name
2. Select record type (A, MX, etc.)
3. View results from worldwide servers
4. Green = propagated, Red = still updating

Command Line:

Mac/Linux:

# Check A record
dig example.com

# Check specific record type
dig example.com MX

# Query specific nameserver
dig @8.8.8.8 example.com

Windows:

# Check A record
nslookup example.com

# Check MX records
nslookup -type=MX example.com

# Query specific DNS server
nslookup example.com 8.8.8.8

Common DNS Issues

Website Not Loading

Symptom: Domain doesn't resolve

Possible Causes:

• A record missing or wrong
• Nameservers incorrect
• DNS not propagated yet
• Records deleted accidentally

Solutions:

1. Verify A Record Exists:

   Check: @ → Your server IP
   Check: www → Your server IP
   

2. Confirm Nameservers:

   dig example.com NS
   

   Should show your DNS provider's nameservers

3. Wait for Propagation:

   • Recent changes? Wait 24-48 hours
   • Check propagation tools

4. Clear DNS Cache:

   # Mac
   sudo dscacheutil -flushcache
   
   # Windows
   ipconfig /flushdns
   
   # Linux
   sudo systemd-resolve --flush-caches
   

Email Not Working

Symptom: Can't send or receive email

Check MX Records:

dig example.com MX

Should See:

example.com. 3600 IN MX 10 mail1.pupam.com.
example.com. 3600 IN MX 20 mail2.pupam.com.

Common Problems:

1. No MX Records:

   • Add MX records pointing to mail servers
   • Set proper priorities

2. Wrong Priority:

   • Lower number = higher priority
   • Adjust if backwards

3. MX Points to CNAME:

   • ❌ MX can't point to CNAME
   • ✅ Must point to A record

4. Missing Email Authentication:

   • Add SPF record
   • Add DKIM record
   • Add DMARC record

Test Email Records:

# Check MX
dig example.com MX

# Check SPF
dig example.com TXT | grep spf

# Check DKIM
dig default._domainkey.example.com TXT

Intermittent Issues

Symptom: Sometimes works, sometimes doesn't

Likely Causes:

1. DNS Propagation in Progress:

   • Different DNS servers have different data
   • Wait for full propagation

2. Low TTL During Changes:

   • Intentional during migration
   • Will stabilize after changes complete

3. ISP DNS Caching:

   • Some ISPs cache aggressively
   • Use public DNS (8.8.8.8, 1.1.1.1)

4. Multiple A Records:

   • Round-robin causing confusion
   • One server down?

Solutions:

• Wait 48 hours
• Use lower TTL temporarily
• Switch to public DNS servers
• Check all servers are up

SSL/HTTPS Issues

Symptom: SSL certificate errors

DNS-Related Causes:

1. Wrong A/AAAA Record:

   • Domain points to wrong server
   • SSL certificate doesn't match

2. Missing CAA Record:

   • Some CAs require CAA
   • Add CAA record for your CA

3. Subdomain Not Configured:

   • Certificate covers www but DNS only has @
   • Or vice versa

Solutions:

# Ensure both root and www covered
A: @ → 192.0.2.1
CNAME: www → example.com

# Add CAA record
CAA: @ → 0 issue "letsencrypt.org"

DNS Cache Issues

Why Caching Causes Problems:

Where DNS is Cached:

• Your computer/device
• Your router
• Your ISP
• Public DNS servers (8.8.8.8)
• CDN edge servers

Clear All Caches:

Your Computer:

# Mac
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

# Windows
ipconfig /flushdns

# Linux (Ubuntu/Debian)
sudo systemd-resolve --flush-caches

# Linux (older)
sudo /etc/init.d/nscd restart

Your Browser:

Chrome: chrome://net-internals/#dns → Clear
Firefox: about:networking#dns → Clear
Safari: Quit and restart browser

Router:

• Restart router
• Or wait 24 hours

Can't Clear:

• ISP cache (wait)
• Public DNS cache (wait)
• Set lower TTL before changes

DNS Security Best Practices

Protect Against DNS Hijacking

Security Measures:

Enable Registry Lock

• Prevents unauthorized transfers
• Requires verification to unlock
• Available at registrar

Use Two-Factor Authentication

• Secure registrar account
• Prevent unauthorized access
• Enable for DNS management

Monitor DNS Changes

• Set up change alerts
• Regular DNS audits
• Review access logs

DNSSEC (DNS Security Extensions)

• Cryptographic signing
• Prevents DNS spoofing
• Validates DNS responses

Enable DNSSEC:

1. Check if provider supports it
2. Enable in DNS settings
3. Add DS records at registrar
4. Verify with DNSSEC validators

Email Authentication Setup

Full Email Security:

SPF Record:

v=spf1 include:_spf.pupam.com ~all

• Authorizes mail servers
• Prevents email spoofing
• Required for deliverability

DKIM Record:

v=DKIM1; k=rsa; p=[public-key]

• Cryptographic signature
• Proves email authenticity
• Improves reputation

DMARC Record:

v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com; ruf=mailto:forensics@example.com; pct=100

• Policy enforcement
• Reporting mechanism
• Protects brand reputation

CAA Record:

0 issue "letsencrypt.org"
0 issuewild "letsencrypt.org"
0 iodef "mailto:security@example.com"

• Controls SSL issuance
• Prevents fraudulent certificates
• Security best practice

Regular DNS Audits

Monthly Checklist:

• Review all DNS records
• Remove unused subdomains
• Verify email authentication
• Check nameserver configuration
• Test website accessibility
• Validate SSL certificates
• Review CAA records
• Check for unauthorized changes
• Verify TTL settings appropriate
• Test email delivery

Use Tools:

• MXToolbox DNS Check
• DNSstuff Tools
• Security Headers checker
• SSL Labs test

DNS Migration Guide

Moving to New Hosting

Safe Migration Process:

Phase 1: Preparation (Before)

1. Document Current Setup:

   • Export all DNS records
   • Screenshot DNS panel
   • Note TTL values
   • List all subdomains

2. Lower TTL Values:

   • Change to 300 seconds (5 minutes)
   • Wait 24-48 hours before migration
   • Ensures fast updates during switch

3. Set Up New Hosting:

   • Get new server IP address
   • Configure server completely
   • Test with hosts file edit

4. Test New Server:

   # Edit hosts file temporarily
   192.0.2.99 example.com
   

   • Verify site works
   • Test all functionality

Phase 2: Migration (During)

1. Update A Records:

   Old: @ → 192.0.2.1
   New: @ → 192.0.2.99
   
   Old: www → 192.0.2.1
   New: www → 192.0.2.99
   

2. Keep Everything Else:

   • Don't change MX records
   • Don't change TXT records
   • Don't change other records

3. Monitor Propagation:

   • Use DNS checker tools
   • Test from multiple locations
   • Check every 15-30 minutes

4. Keep Old Server Running:

   • Don't shut down immediately
   • Traffic will gradually shift
   • Wait 48 hours minimum

Phase 3: Verification (After)

1. Test All Functionality:

   • Visit website from multiple devices
   • Test from mobile and WiFi
   • Check all subdomains
   • Verify forms and checkout

2. Monitor Traffic:

   • Watch server logs
   • Confirm traffic on new server
   • Old server traffic should decrease

3. Restore Normal TTL:

   • After 48-72 hours
   • Change back to 3600 or higher
   • Reduces DNS query load

4. Decommission Old Server:

   • After 7 days minimum
   • Confirm zero traffic
   • Backup any data first

Changing DNS Providers

Switch DNS Management:

Current Setup:

Nameservers: ns1.oldprovider.com
DNS Records: At old provider

Target Setup:

Nameservers: ns1.pupam.com
DNS Records: At PUPAM

Migration Steps:

1. Copy All DNS Records:

   • Export from old provider
   • Document everything
   • Include TTL values

2. Set Up at New Provider:

   • Import/recreate all records
   • Verify exact match
   • Test before switching

3. Lower TTLs (Optional but Recommended):

   • At old provider
   • Wait 24-48 hours
   • Enables faster rollback if needed

4. Change Nameservers at Registrar:

   Old: ns1.oldprovider.com, ns2.oldprovider.com
   New: ns1.pupam.com, ns2.pupam.com
   

5. Wait for Propagation:

   • Check with DNS tools
   • Monitor globally
   • 24-48 hours typical

6. Keep Old Records Active:

   • Don't cancel old provider yet
   • Wait 7 days
   • Ensures smooth transition

7. Verify and Cleanup:

   • Confirm all services work
   • Test email delivery
   • Cancel old DNS service

DNS Performance Optimization

Choose Optimal TTL

TTL Strategy:

High TTL (86400 = 24 hours):

• ✅ Stable, unchanging records
• ✅ Reduces DNS query load
• ✅ Faster for repeat visitors
• ❌ Slow updates when changes needed

Medium TTL (3600 = 1 hour):

• ✅ Good balance
• ✅ Reasonable update time
• ✅ Moderate query load
• 👍 Recommended for most sites

Low TTL (300 = 5 minutes):

• ✅ Fast updates
• ✅ Good for testing
• ✅ Easy migration/failover
• ❌ More DNS queries
• ❌ Slightly slower (cache misses)

Very Low TTL (60 = 1 minute):

• ✅ Dynamic DNS
• ✅ Instant failover
• ❌ High query volume
• ❌ Performance impact

Best Practice:

• Normal operations: 3600 (1 hour)
• Before changes: 300 (5 minutes)
• During migration: 300 (5 minutes)
• After migration: Back to 3600

Use Multiple Nameservers

Why Multiple Nameservers:

• Redundancy if one fails
• Geographic distribution
• Load distribution
• Better availability

Minimum: 2 nameservers Recommended: 4 nameservers

Our Nameservers:

ns1.pupam.com (US East)
ns2.pupam.com (US West)
ns3.pupam.com (Europe)
ns4.pupam.com (Asia)

Benefits:

• 99.99% uptime
• Global performance
• Automatic failover
• Low latency worldwide

Implement DNS Prefetching

Speed Up External Resources:

In HTML <head>:

<!-- Prefetch DNS for external resources -->
<link rel="dns-prefetch" href="//cdn.example.com">
<link rel="dns-prefetch" href="//fonts.googleapis.com">
<link rel="dns-prefetch" href="//analytics.google.com">
<link rel="dns-prefetch" href="//ajax.googleapis.com">

Benefits:

• Resolves DNS before needed
• Faster resource loading
• Improved page speed
• Better user experience

When to Use:

• External fonts
• CDN resources
• Analytics scripts
• Third-party APIs

Frequently Asked Questions

How long does DNS propagation take?

Typically 1-2 hours for most users, but can take up to 48 hours globally. Factors: TTL values, ISP caching policies, geographic location.

Can I change DNS records without downtime?

Yes, if done carefully:

• Lower TTL 24-48 hours before
• Set up new configuration completely
• Test before switching
• Make changes during low-traffic hours

What's the difference between DNS and nameservers?

Nameservers host your DNS records. DNS records are the actual instructions (A, MX, etc.). Think of nameservers as the file cabinet and DNS records as the files inside.

Do I need to change nameservers to use your email?

No! You can keep your current nameservers and just add/modify MX records and email authentication records (SPF, DKIM, DMARC).

Can I use Cloudflare with your hosting?

Yes! Point your domain to Cloudflare nameservers, then add A records pointing to our server IPs. Cloudflare will proxy traffic through their CDN.

What happens if I delete all DNS records?

Your website and email will stop working. DNS records tell the internet where to find your services. Always backup records before making changes.

How do I test DNS changes before going live?

Edit your computer's hosts file to point domain to new IP temporarily. This lets you test without affecting real DNS:

# Add to hosts file
192.0.2.99 example.com

Why is DNS working in some places but not others?

DNS propagation is in progress. Different locations update at different times. Use whatsmydns.net to check propagation status worldwide.

Quick Reference

Essential DNS Records Checklist

Basic Website:

• A record: @ → Your server IP
• A or CNAME: www → Your server IP or domain

Email Configuration:

• MX records (2-3 with priorities)
• TXT record: SPF
• TXT record: DKIM
• TXT record: DMARC

Security:

• CAA record for SSL authority
• Enable DNSSEC (if available)
• Two-factor auth on DNS account

Best Practices:

• Use 4 nameservers
• Set appropriate TTL (3600 default)
• Document all records
• Regular security audits

Common DNS Record Syntax

Troubleshooting Commands

Need DNS help? Contact our technical team at dns-support@pupam.com

24/7 DNS Support: Create a ticket → or call +1 (555) 123-SUPPORT

Useful Tools: DNS Checker → | MX Toolbox → | What's My DNS →