DNS Configuration Basics

Understanding how DNS routing works with AtomicEdge protection.

What DNS Configuration Does

Traffic Flow Change

Before AtomicEdge:

Visitor → Your Server

After AtomicEdge:

Visitor → AtomicEdge WAF → Your Server

Result: All malicious traffic is blocked before reaching your server.

Getting Your WAF Endpoint

From Your Dashboard

1. Go to Sites and select your website
2. Copy your WAF Endpoint IP (e.g., 198.51.100.10)
3. Note the endpoint hostname (alternative to IP)

What You'll Use

• WAF Endpoint IP: The IP address to point your domain to
• Endpoint Hostname: Alternative CNAME target (optional)
• Backend IP: Your original server IP (stays the same)

DNS Record Types

A Record (Recommended)

• Purpose: Points domain directly to IP address
• Best for: Most websites and standard setups
• Example: example.com → 198.51.100.10

CNAME Record

• Purpose: Points domain to another hostname
• Best for: Complex setups or when IP might change
• Example: example.com → waf-endpoint-abc123.atomicedge.io

Why This Step is Critical

Without Proper DNS

• No Protection: Traffic goes directly to your server
• WAF Bypassed: Attackers can reach your server directly
• Dashboard Shows Inactive: Protection status remains "DNS Pending"

With Proper DNS

• Full Protection: All traffic filtered through WAF
• Attack Blocking: Malicious requests stopped automatically
• Dashboard Shows Active: Protection status becomes "Active"

Next Steps

• Update DNS Records - Make the actual DNS changes
• Handle Subdomains - Configure www, blog, shop, etc.
• Verify Changes - Confirm DNS is working

Need Help?

• 💬 Live Chat: Get help understanding DNS basics
• 📧 Email Support: support@atomicedge.io