If you’re trying to test a site behind an AWS Application Load Balancer (ALB) before a DNS cut-over, NextDNS is one of the simplest ways to do it. Instead of modifying hosts files or configuring local networking on every machine involved in testing, you can just create a DNS rewrite in NextDNS and share the configuration with anyone who needs access. This works especially well in agency environments where developers, project managers, and clients all need to preview a site before launch.
The idea is simple: you tell NextDNS that a domain should resolve to your ALB’s DNS address, and anyone using your shared NextDNS configuration will resolve the domain that way. From their perspective, the site just works normally, exactly how it will after the DNS cut-over.
Here’s the quick way to set it up:
- Create a NextDNS account
Go to https://nextdns.io and create a configuration. - Add a DNS Rewrite
In the configuration dashboard, add a rewrite so your domain points to the ALB DNS address. Example:staging.example.com → your-alb-123456.us-east-1.elb.amazonaws.com - Share your Configuration ID
NextDNS provides a configuration ID that can be shared with teammates or clients. - Have testers install NextDNS
They install the NextDNS app and enter the configuration ID in preferences. On macOS, this shows up as a small shield icon in the menu bar when active. - Test the site normally
Once enabled, the domain resolves through NextDNS and points to the ALB. No hosts file edits, no VPN tricks, and no local dev network configuration required.
This approach makes pre-launch testing much smoother because everyone sees the environment the same way. It behaves just like a DNS change would in something like Cloudflare, except you can control exactly who sees it.
One final thing to keep in mind: if you’re sharing this with clients or customers, make sure their IT policies allow the use of NextDNS. Some organizations restrict custom DNS tools, so it’s worth confirming before asking them to install it.
Leave a Reply