use of "classification" field

[bastiaanvisser]

What is the use of the "Classification" field when adding a zone (or editing its options), and is it somehow possible to disable this field (or make it optional)?

[Napsty]

Was just about to create an issue to ask the same question.

[thomas-pike]

This field was created and used by Opera Software. In their case it was used to distinguish between internal zones (that should only be synced out to the internal resolvers) and public zones (that should be synced to all resolvers and the public nameservers). Other companies will likely not have a setup like this, and so for them the field is not very useful (though providing any value at all in the field will suffice). If we are to make the field optional/hidden, it will have to be done by adding a configuration setting for it.

[Napsty]

Or you could just rename the field from "classification" to "description"? The field itself seems to be irrelevant for the actual zone, but a description field is always nice to have. But yes, it should be optional.

[robertpenz]

Please keep it as "classification" and not "description". We've the same use case as Opera. Some domains are only internal for 10.* IP addresses and domains are replicated to our external servers.

[thomas-pike]

Don't worry, I have no intention of renaming the field, as Opera would not be happy with me breaking upgrades for them. I expect the simplest option is to make a configuration setting with 3 options for the field: required / optional / disabled

[jsoref]

If you could make it optional, that would be great. Right now, I have a dozen domains, only the most recent has a classification, and that's because I couldn't create a zone using dns-ui w/o filling out that field.