DNS Requests are the core of DNSDone: they let you define, share, and track DNS changes without endless email threads or screenshots.
Each request represents a specific set of DNS record updates for a domain or subdomain and keeps everyone aligned from start to finish.
What a DNS request is
A DNS request is a shared workspace for DNS changes.
It includes:
- The domain or subdomain you’re working on
- The DNS records that need to be added, edited, or removed
- The recipients responsible for applying those changes
- The status and timeline showing progress over time
Everything is tracked automatically, so you can see exactly what’s been done and when.
Why DNS requests matter
Instead of sending DNS instructions manually, a request gives you a structured, traceable way to manage them.
Benefits:
- Clear communication – everyone sees the same DNS record list.
- No guesswork – recipients get precise instructions.
- Built-in tracking – automatic propagation checks confirm completion.
- Fewer errors – no more outdated instructions or missing records.
How requests fit into your workflow
- Create a request for a specific domain.
- Add DNS records that describe the changes.
- Share the request with your client or DNS admin.
- Track the request as it’s implemented and verified.
- Review the results automatically once propagation is complete.
Each step is logged and visible in the timeline — you always know the status of every change.
Who uses DNS requests
DNS requests are built for teams that coordinate DNS changes between:
- Web agencies and their clients
- Developers and hosting providers
- IT teams managing multiple domains
- Anyone who needs visibility into DNS updates