diff --git a/lam/HISTORY b/lam/HISTORY
index fb8e7ab9..3a01827c 100644
--- a/lam/HISTORY
+++ b/lam/HISTORY
@@ -3,7 +3,7 @@ March 2019
- Support logging to remote syslog server
- LAM Pro:
-> New self service fields: Mail routing (Local address) and Windows (Proxy-Addresses)
- -> Bind DLZ: support DNAME records and descriptions in records (requires latest LDAP schema)
+ -> Bind DLZ: support DNAME+XFR records and descriptions in records (requires latest LDAP schema)
- Fixed bugs:
-> Allow tree-only configurations without any other tab
diff --git a/lam/docs/manual-sources/chapter-modules.xml b/lam/docs/manual-sources/chapter-modules.xml
index 4a35a61f..ea2ff5c7 100644
--- a/lam/docs/manual-sources/chapter-modules.xml
+++ b/lam/docs/manual-sources/chapter-modules.xml
@@ -4103,373 +4103,416 @@ Run slapindex to rebuild the index.
url="https://gitlab.isc.org/isc-projects/bind9/blob/master/contrib/dlz/modules/ldap/testing/dlz.schema">git
repository.
- Configuration
+
+ Configuration
- First, you need to add the Bind DNS account type and the Bind DLZ
- module:
+ First, you need to add the Bind DNS account type and the Bind DLZ
+ module:
-
-
-
-
-
-
-
+
+
+
+
+
+
+
- Please set the LDAP suffix either to an existing DNS zone (dlzZone)
- or an organizational unit that should include your DNS zones.
+ Please set the LDAP suffix either to an existing DNS zone
+ (dlzZone) or an organizational unit that should include your DNS
+ zones.
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+
-
-
-
-
-
-
-
+ For regular entry management use "DNS entry (bindDLZ)(*)"
+ module.
- Automatic PTR management
+
+
+
+
+
+
+
- LAM can automatically create/delete PTR entries for the entered
- IPv4/6 records. You can enable this feature on the module settings
- tab.
+ XFR
- PTR records will get the same TTL as IP records. Please note that
- you need to have matching reverse zones (".in-addr.arpa"/".ip6.arpa")
- under the same suffix as your other DNS entries.
+ If you want to edit XFR entries please add a second account type
+ for XFR. Recommended list attributes are
+ "#dlzipaddr;#dlzrecordid".
-
-
-
-
-
-
-
+
+ ![]()
+
- Zone management
+ Now use the "XFR (bindDLZXfr)(*)" module for this account
+ type.
- If you do not yet have a DNS zone then LAM can create one for you.
- In list view switch the suffix to an organizational unit DN. Now you will
- see a button "New zone".
+
+ ![]()
+
- This will create the zone container entry and a default DNS entry
- "@" for authoritative information. Now switch the suffix to your new zone
- and start adding DNS entries.
+ Automatic PTR management
-
-
-
-
-
-
-
+ LAM can automatically create/delete PTR entries for the entered
+ IPv4/6 records. You can enable this feature on the module settings
+ tab.
- DNS entries
+ PTR records will get the same TTL as IP records. Please note that
+ you need to have matching reverse zones (".in-addr.arpa"/".ip6.arpa")
+ under the same suffix as your other DNS entries.
- LAM supports the following DNS record types:
+
+
+
+
+
+
+
-
-
- SOA: authoritative information
-
+ Zone management
-
- NS: name servers
-
+ If you do not yet have a DNS zone then LAM can create one for you.
+ In list view switch the suffix to an organizational unit DN. Now you
+ will see a button "New zone".
-
- A/AAAA: IP addresses
-
+ This will create the zone container entry and a default DNS entry
+ "@" for authoritative information. Now switch the suffix to your new
+ zone and start adding DNS entries.
-
- PTR: reverse DNS entries
-
+
+
+
+
+
+
+
+
-
- CNAME: alias names
-
+
+ DNS entries
-
- MX: mail servers
-
+ LAM supports the following DNS record types:
-
- TXT: text records
-
+
+
+ SOA: authoritative information
+
-
- SRV: service entries
-
-
+
+ NS: name servers
+
-
+
+ A/AAAA: IP addresses
+
+
+
+ PTR: reverse DNS entries
+
+
+
+ CNAME: alias names
+
+
+
+ MX: mail servers
+
+
+
+ TXT: text records
+
+
+
+ SRV: service entries
+
+
+
+
- Authoritative (SOA) and name server (NS)
- records
+ Authoritative (SOA) and name server (NS)
+ records
- Here you can manage general information about the zone like timeouts
- and name servers. Please note that name servers must be inserted in a
- special format (dot at the end).
+ Here you can manage general information about the zone like
+ timeouts and name servers. Please note that name servers must be
+ inserted in a special format (dot at the end).
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+
- IP addresses (A/AAAA)
+ IP addresses (A/AAAA)
- LAM will automatically set the correct type (A/AAAA) depending if
- you enter an IPv4 or IPv6 address.
+ LAM will automatically set the correct type (A/AAAA) depending if
+ you enter an IPv4 or IPv6 address.
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+
- Reverse DNS entries
+ Reverse DNS entries
- Reverse DNS entries are important when you need to find the DNS name
- that is associated with a given IP address. Reverse DNS entries are stored
- in a separate DNS zone.
+ Reverse DNS entries are important when you need to find the DNS
+ name that is associated with a given IP address. Reverse DNS entries are
+ stored in a separate DNS zone.
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+
- Alias names (CNAME)
+ Alias names (CNAME)
- Sometimes a DNS entry should simply point to a different DNS entry
- (e.g. for migrations). This can be done by adding an alias name.
+ Sometimes a DNS entry should simply point to a different DNS entry
+ (e.g. for migrations). This can be done by adding an alias name.
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+
- Mail servers (MX)
+ Mail servers (MX)
- The mail server entries define where mails to a domain should be
- delivered. The server with the lowest preference has the highest
- priority.
+ The mail server entries define where mails to a domain should be
+ delivered. The server with the lowest preference has the highest
+ priority.
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+
- Text records (TXT)
+ Text records (TXT)
- Text records can be added to store a description or other data (e.g.
- SPF information).
+ Text records can be added to store a description or other data
+ (e.g. SPF information).
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+
- Services (SRV)
+ Services (SRV)
- Service records can be used to specify which servers provide common
- services such as LDAP. Please note that the host name must be
- _SERVICE._PROTOCOL (e.g. _ldap._tcp).
+ Service records can be used to specify which servers provide
+ common services such as LDAP. Please note that the host name must be
+ _SERVICE._PROTOCOL (e.g. _ldap._tcp).
-
+
- Priority: The priority of the target host, lower value means more
- preferred.
+ Priority: The priority of the target host, lower value means more
+ preferred.
- Weight: A relative weight for records with the same priority. E.g.
- weights 20 and 80 for a service will result in 20% queries to the one
- server and 80% to the other.
+ Weight: A relative weight for records with the same priority. E.g.
+ weights 20 and 80 for a service will result in 20% queries to the one
+ server and 80% to the other.
- Port: The port number that is used for your service.
+ Port: The port number that is used for your service.
- Server: DNS name where service can be reached (with dot at the
- end).
+ Server: DNS name where service can be reached (with dot at the
+ end).
-
-
-
-
-
-
-
+
+
+
+
+
+
+
-
+
- File upload
+ File upload
- You can upload complete DNS zones via LAM's file upload. Here is an
- example for a zone file and the corresponding CSV file.
+ You can upload complete DNS zones via LAM's file upload. Here is
+ an example for a zone file and the corresponding CSV file.
-
- Zone file
+
+ Zone file
-
-
-
- @
+
+
+
+ @
- IN
+ IN
- SOA
+ SOA
- ns1.example.com admin.ns1.example.com (1 360000 3600
- 3600000 370000)
-
+ ns1.example.com admin.ns1.example.com (1 360000 3600
+ 3600000 370000)
+
-
-
+
+
- IN
+ IN
- NS
+ NS
- ns1.example.com.
-
+ ns1.example.com.
+
-
-
+
+
- IN
+ IN
- NS
+ NS
- ns2.example.com.
-
+ ns2.example.com.
+
-
-
+
+
- IN
+ IN
- MX
+ MX
- 10 mail1.example.com
-
+ 10 mail1.example.com
+
-
-
+
+
- IN
+ IN
- MX
+ MX
- 20 mail2.example.com
-
+ 20 mail2.example.com
+
-
- foo
+
+ foo
- IN
+ IN
- A
+ A
- 123.123.123.100
-
+ 123.123.123.100
+
-
- foo2
+
+ foo2
- IN
+ IN
- CNAME
+ CNAME
- foo.example.com
-
+ foo.example.com
+
-
- bar
+
+ bar
- IN
+ IN
- A
+ A
- 123.123.123.101
-
+ 123.123.123.101
+
-
-
+
+
- IN
+ IN
- AAAA
+ AAAA
- 1:2:3:4:5
-
-
-
-
+ 1:2:3:4:5
+
+
+
+
- Please check that you have an existing zone entry that can be used
- for the file upload. See above to create a new zone.
+ Please check that you have an existing zone entry that can be used
+ for the file upload. See above to create a new zone.
- Hint: If you use the function above to create a new zone then please
- skip the "@" entry in the CSV file below. LAM creates this entry with
- sample data.
+ Hint: If you use the function above to create a new zone then
+ please skip the "@" entry in the CSV file below. LAM creates this entry
+ with sample data.
- In this example we assume that the following zone extry
- exists:
+ In this example we assume that the following zone extry
+ exists:
- dn: dlzZoneName=example.com,ou=bind,dc=example,dc=com
+ dn: dlzZoneName=example.com,ou=bind,dc=example,dc=com
dlzzonename: example.com
objectclass: dlzZone
objectclass: top
- Here is the corresponding CSV file: bindUpload.csv
+ Here is the corresponding CSV file: bindUpload.csv
+
+
+
+ XFR entries
+
+ You can manage the XFR entries in the second tab that you
+ configured before.
+
+
+ ![]()
+
+
+ For each XFR entry you can set a record ID and the IP
+ address.
+
+
+ ![]()
+
+
diff --git a/lam/docs/manual-sources/images/mod_bind13.png b/lam/docs/manual-sources/images/mod_bind13.png
new file mode 100644
index 00000000..744210b1
Binary files /dev/null and b/lam/docs/manual-sources/images/mod_bind13.png differ
diff --git a/lam/docs/manual-sources/images/mod_bind14.png b/lam/docs/manual-sources/images/mod_bind14.png
new file mode 100644
index 00000000..c8873a9a
Binary files /dev/null and b/lam/docs/manual-sources/images/mod_bind14.png differ
diff --git a/lam/docs/manual-sources/images/mod_bind15.png b/lam/docs/manual-sources/images/mod_bind15.png
new file mode 100644
index 00000000..25e4bb8c
Binary files /dev/null and b/lam/docs/manual-sources/images/mod_bind15.png differ
diff --git a/lam/docs/manual-sources/images/mod_bind16.png b/lam/docs/manual-sources/images/mod_bind16.png
new file mode 100644
index 00000000..f9ef55df
Binary files /dev/null and b/lam/docs/manual-sources/images/mod_bind16.png differ