I've noticed to my surprise that a vhost name containing an underscore breaks the zone to the point bind9 will simply not serve any of it. I'm not sure this is documented (didn't check) and this is also not covered from the zone validation scripts.

We should find out more about the issue and perhaps add an extra check made by gitzone, reporting the error and breaking the validation of the zone pu

To be 100% transparent, maybe an explanation why some exception are made should be added to the repository. For example:

• a
• rf
• sm

Why these domains exists, given the restriction published (Name-Restrictions)? Given these, why others (like #74 or moderntld/.o#122) are rejected?

I'm weighing in on whether the keywords for named.conf should be all-white if obsoleted; or some kind of user-definable color?

Feel free to chime in.

It's not clear how to do the following:

When updating DNS, apply your changes to LDAP, and then run make. It will rebuild the primary DNS (db.ocf) and reverse DNS, including pulling host data from LDAP and bumping the serial number.

i think the command is just ldapvi cn=lb or something?

Hi,

I was trying to open a configuration file, from a bind installed on Cent-OS, encountered such an error:
pyparsing.ParseSyntaxException: Expected <boolean>, found '-'

I checked the file; Error hit on this property:
memstatistics-file

Decided to run the provided example parse_bind9, to be sure my code