Changeset 1323 for trunk/LATMOS-Accounts/man/man8/latmos-accounts-base-sql.pod

Timestamp:

04/08/15 16:47:40 (9 years ago)

Author:

nanardon

Message:

More documentation

File:

• trunk/LATMOS-Accounts/man/man8/latmos-accounts-base-sql.pod (modified) (1 diff)

trunk/LATMOS-Accounts/man/man8/latmos-accounts-base-sql.pod

@@ -11 +11 @@
 
 =head1 FEATURES
+
+=head2 Network managment
+
+Link::Accounts can build automatically some part of your DNS or DHCP
+configuration.
+
+To do this you have to create a C<netzone> object. Such object need a type:
+
+=over 4
+
+=item dns: to build a DNS zone for classic domain
+
+=item reverse: for reverse IP address (168.192.in-addr.arpa)
+
+=item dhcp: ISC dscpd configuration for fixed address
+
+=item puppet: puppet configuration
+
+=over4
+
+The way it works is quite simple, each zone will make the code to write a file
+you can include in your server configuration. The match is done by looking the
+zone IP address masks and the host IPs.
+
+For example someone having a zone named C<private.mydomain.com> having masks
+C<192.168.5.0/24>, and having an host named C<foo> with IP C<192.168.5.3> and
+another host C<bar> with IP C<192.168.13.78>. The zone built will look likes:
+
+    foo IN A 192.168.5.3
+
+As you can see this DNS zone is not valid: the goal of such feature is to make
+the repetive work for us, not to manage the full zone (even such feature could
+be possible). The repetitive work is declaring the hundred computers our users
+have.
+
+The output will be happend to a template have the name of the zone suffixed by
+C<.in>. You can put in this template evering about the zone declaration (SOA,
+NS, TXT...).
 
 =head2 Group AutoMemberFilter