Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MM-30515. Updated BIND parser. #310

Open
wants to merge 2 commits into
base: latest
Choose a base branch
from

Conversation

rachelbritton
Copy link
Collaborator

Updated BIND parser reference article. Please review to make sure the content is correct and restructuring makes sense.

Updated BIND parser reference article.
Fixed some grammar and formatting inconsistencies.

Checked content against https://bluecatnetworks.atlassian.net/browse/MM-30144 to make sure all the customer's questions are addressed.

The current version of the Men&Mice Management Console has no interface to change the values of the following statements: ``key``, ``acl``, ``controls``, ``server``, ``trusted-keys``. Therefore, they are kept in separate files, ``user_before`` and ``user_after``. Micetro does *not* modify these files.
If both of these criteria are met, the parser assumes that configuration has been arranged and behaves accordingly.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "arrange" command of the installer behaves accordingly not the parser, right? @indridib

5. /etc/local/sbin
6. /etc/opt/isc/isc-bind
7. /etc/opt/isc/scls/isc-bind

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add a note on how to overwrite/specify a different path? I.e. by adding an XML-tag for each statement
<named-checkconf value="/path to the /named-checkconf"/>
<named-checkzone value="/path to the /named-checkzone"/>

Should we mention also that it is the preferences.cfg file of the DNS Server Controller agent?

@@ -1,53 +1,204 @@
.. meta::
:description: When Micetro is installed on a server running BIND, it needs to perform several changes to the server configuration file structure. This section describes these changes and includes an overview diagram that shows how the server configuration files are processed
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
:description: When Micetro is installed on a server running BIND, it needs to perform several changes to the server configuration file structure. This section describes these changes and includes an overview diagram that shows how the server configuration files are processed
:description: When Micetro is installed on a server running BIND, it will perform several changes to the server configuration file structure. This section describes these changes and includes an overview diagram that shows how the server configuration files are processed

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't need to any more, but it will by default arrange the files.

``named.conf`` is split into several files. A new ``named.conf`` file that includes statements for all the new files is created.
Arranging the Configuration and Files
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The parser's arranger splits the configuration into two files:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not two files. It's a single file named.conf and then a directory containing the configuration

.. note::
BWD is the BIND Working Directory, the location specified in the options directory statement. If no directory statement is found, the current directory is assumed unless you specify the root directory (-r argument). If the root directory is specified, Micetro will assume relative to the root.

When started, the parser detects whether the directory ``<BWF>/conf/zones`` exists and whether the initial configuration file (typically ``named.conf``) contains one of the following phrases:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When started, the parser detects whether the directory ``<BWF>/conf/zones`` exists and whether the initial configuration file (typically ``named.conf``) contains one of the following phrases:
When started, the parser detects whether the directory ``<BWD>/conf/zones`` exists and whether the initial configuration file (typically ``named.conf``) contains one of the following phrases:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants