History & requests helps you see what changed, what is still running and what needs approval. It is also where a scheduled DNS change can be checked before its intended execution time.
IN THIS ARTICLE
01 Read an operation correctly
Open the selected domain and inspect the change's date, status and affected records. A draft or preview has not changed public DNS. Scheduled work is waiting for its time. Applying work is still being sent to or verified against the provider. A failed entry should include a reason or retry information. Review that detail before issuing the same change again.
Public DNS propagation is a separate stage. A completed provider change can coexist with old answers in recursive caches. Use the propagation action to distinguish a cache delay from a change that never reached the DNS server.
02 Schedule a supported change
- Prepare the intended record change in the editor or bulk workflow.
- Review the resulting record plan carefully.
- When the confirmation screen offers scheduling, choose a future time. Check the timezone shown by the interface and translate your maintenance window accordingly.
- Confirm the scheduled request.
- Open History & requests and verify the saved time and status.
- After the scheduled time, inspect the result and test the affected service.
Scheduling depends on your access and the available workflow. If the option is not present, do not assume that entering a time elsewhere schedules DNS. Contact support when you need a coordinated change that your view cannot schedule.
Can I cancel a scheduled DNS change or undo a completed one?
Use the cancellation action while a change is still scheduled. Refresh the history afterwards to confirm it was cancelled. Once application has begun, cancellation may no longer be possible. Prepare a new correcting change from the actual confirmed records instead of assuming the earlier action was undone.
Eligible Premium DNS subscriptions can provide Undo for supported history entries. Undo itself creates and validates a new DNS change. It does not roll back unrelated edits, registrar settings or external application state. For several intertwined changes, preview a managed backup restore or ask support to compare the configurations.
03 When requesting help
Include the domain, approximate time, operation reference, status and visible error. State the intended record and destination, with credentials removed. This makes it possible to follow the exact change rather than guess from a screenshot of the current record list.