Hi, I’m using VirtualmIn 3.94.gpl on Debian 7, (we’re migrating to a new server) and while I can make any other change I like in DNS records on our server, trying to update bulk records with Servers -> BIND DNS Server -> Find Zones Matching -> Update Records in Selected, will fail with the error message “Failed to update zones: Zone does not exist!”
Yet, what do you know, that zone does exist, and I can modify it any way I like. Just not with the tool that lets me update multiple DNS zones. Which is pretty important when you need to update a lot of DNS zones to a new server!
Attached are some helpful screenshots, including the Call Stack Trace showing the final error message.
Hmm, it sounds like you may be seeing a bug there. But it also looks like the Virtualmin version you’re using there is a bit over 2 years old.
Would it be possible to upgrade to the most recent Webmin and Virtualmin versions? There’s an excellent chance that issue is corrected in the most recent versions of that software (I’d recommend upgrading both Webmin and Virtualmin).
And then, if that doesn’t correct it, we can dig a bit more into what’s going on there, and possibly get Jamie involved if need be.
Funny you should mention that! The new server we’re migrating these zones to is the latest version (4.11.gpl), and it appears to be behaving the same way.
It seems a little odd to me that noone would use this feature in the past two years? Or maybe it’s our zone files? It’s also weird that modifying the zones any other way works fine.
Actually, the error is slightly different in the new version:
“Failed to update zones : Zone 173 in view external does not exist!”
This is still pretty important!