I hope you reconsider the severity of this bug and fix it promptly. It's not unlikely several more admins will make the same mistake on live sites, potentially leading to severe business damage.
This is a severe bug which caused me to accidentally overwrite all the DNS entries for a production website yesterday. By the time I had discovered the problem, the incorrect records had already propagated resulting in site downtime and bouncing emails (caused by the incorrect MX records).
As a result of this, I will be switching all of my DNS hosting to a 3rd party solution.
The simplest solution to this bug is probably to include the domain_id being edited in the form data (perhaps with a hidden HTML field), rather than retrieving it from the session/cookie/database. Implemented this way, posts from the DNS edit page would be stateless (as they should be) and the behavior of this tool would be as expected.
Thank you for your feedback and attention. The system is designed to allow editing one DNS settings at a time. You need to refresh your page to see which domain is being edited. There is no short term plan to change it, but we will update you if we made any changes.
Best Regards,
Dynadot Staff
[This post has been edited by dynadot_staff on Nov 24, 2010 11:17am.]