Cloudmin Services requires "Maximum zones" to be filled in

Not sure why we're forcing users to choose a maximum here? I guess if the plan is to always auto-scale up in the event you reach the limit...but people aren't going to realize you can host a couple hundred thousand low-load zones on a single VM, assuming sufficient memory, so they'll make dumb decisions there, anyway.

I reckon if the value is empty, then there should be no limit.

Status: 
Closed (fixed)

Comments

Yeah, for DNS zones I can see having no limit makes more sense. I'll allow the user to select "unlimited" in the next release of the Cloudmin Services module.

Automatically closed -- issue fixed for 2 weeks with no activity.