Not sure if it's a bug or a feature request, but submitting as a bug report as I'm not seeing at least user feedback.
From virtualmin UI(Server Configuration->DNS Records), changing/adding/deleting a DNS record in a domain that is configured as a dynamic domain(allow-update in zone config), the zone is not frozen properly to actually commit the changes. No feedback is given to the user. It must be frozen(rndc freeze), reloaded, then thawed(thaw).
However, in Webmin->Servers->Bind, editing and reloading a dynamic zone without freeze/thaw does give an error back to the user.
In limited testing, I was able to freeze/edit/reload/thaw a non-dynamic zone without a complaint from bind or rndc.
I'd ask that at the least, virtualmin checks for a dynamic zone upon editing, and properly freeze/change/reload/thaw the domain. Ideally, of course, both virtualmin and webmin would do it without the user having to guess whether a domain is dynamic.
Of course other thoughts would be to add freeze/thaw options to the UI where appropriate, or to add an option in BIND config to "Always freeze/reload/thaw on reload" defaulting to off.(would that apply in virtualmin as well?)
Thanks!
Comments
Submitted by JamieCameron on Thu, 08/04/2011 - 00:02 Comment #1
This exact issue will be fixed in Webmin 1.560, which will be released in a few days ..
Submitted by Locutus on Thu, 08/04/2011 - 04:21 Comment #2
Take a look at this. :)
http://www.virtualmin.com/node/18338
Submitted by zignut on Thu, 08/04/2011 - 06:06 Pro Licensee Comment #3
Jamie, what is the behavior? I went looking for a xhangelog to see how it was handled but came up empty
Submitted by zignut on Thu, 08/04/2011 - 08:53 Pro Licensee Comment #4
Nevermind, found the changelog I was looking for! Much thanks!
Submitted by Issues on Thu, 08/18/2011 - 09:23 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.