WAFGOPreparing your page
DNS · Integration and routing guide

DNS integration, resolution and routing guide

Understand DNS records, TTLs, domain integration and change verification when preparing a reversible CDN cutover or recovery plan.

Overview

Before visitors receive content, they need to find the correct entry point. Review DNS, certificates and CDN configuration as one integration plan so individual correct settings form a working chain.

This is a DNS integration and evaluation guide. It does not announce standalone authoritative DNS, programmable records or custom nameserver products. Confirm available hosting and routing features individually.

01

Inventory records and their responsibilities

Websites, email, validation records and delegated subdomains serve different purposes. Change only relevant records when connecting a CDN so website work does not disrupt another service.

Inventory records and their responsibilities
Record or settingCheck
Website resolutionTarget address, alias chain and current hosting restrictions
Email and validationExisting records required by other services
TTLCache duration and the change window
CertificatesRequested names, certificate coverage and validation
02

Make DNS changes verifiable and reversible

Resolver caches do not update everywhere at the same moment. Plan the change window and keep old and new entry points working during the transition.

  • Record the original DNS and application settings, with clear owners for changes and verification.
  • Validate certificates, content and permissions at the destination before switching.
  • Observe resolution from multiple real networks rather than only a local cache.
  • Allow for cached answers during rollback instead of assuming an instant reversal.
03

Distinguish DNS routing from request routing

DNS decisions are affected by resolver caching, while connection or application routing happens later. Define the boundaries for failure detection, propagation and recovery when choosing an approach.

Health signals

Use checks that reflect application health rather than relying only on an open port.

Failover

Verify the alternate entry point completely and exercise the transition while some clients still hold old answers.

Access management

Limit who can change records, retain change history and review access regularly.

Frequently asked questions

No. A lower value can increase queries and does not guarantee immediate updates everywhere. Choose based on change frequency and observed resolution behavior.

Recursive resolvers, systems or applications may retain cached answers. Also review alias chains, resolution sources and the actual response from both entry points.

Start with your requirements

Make the architecture work for your business

Share your audience regions, content types and current challenges with WAFGO to clarify prerequisites, service scope and validation.

Discuss my requirements