XFR
This commit is contained in:
parent
1eac04648a
commit
ab12d24703
|
@ -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
|
||||
|
||||
|
|
|
@ -4103,7 +4103,8 @@ 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</ulink>.</para>
|
||||
|
||||
<para><emphasis role="bold">Configuration</emphasis></para>
|
||||
<section>
|
||||
<title>Configuration</title>
|
||||
|
||||
<para>First, you need to add the Bind DNS account type and the Bind DLZ
|
||||
module:</para>
|
||||
|
@ -4116,8 +4117,9 @@ Run slapindex to rebuild the index.
|
|||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>Please set the LDAP suffix either to an existing DNS zone (dlzZone)
|
||||
or an organizational unit that should include your DNS zones.</para>
|
||||
<para>Please set the LDAP suffix either to an existing DNS zone
|
||||
(dlzZone) or an organizational unit that should include your DNS
|
||||
zones.</para>
|
||||
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
|
@ -4130,6 +4132,9 @@ Run slapindex to rebuild the index.
|
|||
<literallayout>
|
||||
</literallayout>
|
||||
|
||||
<para>For regular entry management use "DNS entry (bindDLZ)(*)"
|
||||
module.</para>
|
||||
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
|
@ -4138,6 +4143,23 @@ Run slapindex to rebuild the index.
|
|||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para><emphasis role="bold">XFR</emphasis></para>
|
||||
|
||||
<para>If you want to edit XFR entries please add a second account type
|
||||
for XFR. Recommended list attributes are
|
||||
"#dlzipaddr;#dlzrecordid".</para>
|
||||
|
||||
<screenshot>
|
||||
<graphic fileref="images/mod_bind13.png"/>
|
||||
</screenshot>
|
||||
|
||||
<para>Now use the "XFR (bindDLZXfr)(*)" module for this account
|
||||
type.</para>
|
||||
|
||||
<screenshot>
|
||||
<graphic fileref="images/mod_bind14.png"/>
|
||||
</screenshot>
|
||||
|
||||
<para><emphasis role="bold">Automatic PTR management</emphasis></para>
|
||||
|
||||
<para>LAM can automatically create/delete PTR entries for the entered
|
||||
|
@ -4159,12 +4181,12 @@ Run slapindex to rebuild the index.
|
|||
<para><emphasis role="bold">Zone management</emphasis></para>
|
||||
|
||||
<para>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".</para>
|
||||
In list view switch the suffix to an organizational unit DN. Now you
|
||||
will see a button "New zone".</para>
|
||||
|
||||
<para>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.</para>
|
||||
"@" for authoritative information. Now switch the suffix to your new
|
||||
zone and start adding DNS entries.</para>
|
||||
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
|
@ -4173,8 +4195,10 @@ Run slapindex to rebuild the index.
|
|||
</imageobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</section>
|
||||
|
||||
<para><emphasis role="bold">DNS entries</emphasis></para>
|
||||
<section>
|
||||
<title>DNS entries</title>
|
||||
|
||||
<para>LAM supports the following DNS record types:</para>
|
||||
|
||||
|
@ -4218,9 +4242,9 @@ Run slapindex to rebuild the index.
|
|||
<para><emphasis role="bold">Authoritative (SOA) and name server (NS)
|
||||
records</emphasis></para>
|
||||
|
||||
<para>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).</para>
|
||||
<para>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).</para>
|
||||
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
|
@ -4251,9 +4275,9 @@ Run slapindex to rebuild the index.
|
|||
|
||||
<para><emphasis role="bold">Reverse DNS entries</emphasis></para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>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.</para>
|
||||
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
|
@ -4301,8 +4325,8 @@ Run slapindex to rebuild the index.
|
|||
|
||||
<para><emphasis role="bold">Text records (TXT)</emphasis></para>
|
||||
|
||||
<para>Text records can be added to store a description or other data (e.g.
|
||||
SPF information).</para>
|
||||
<para>Text records can be added to store a description or other data
|
||||
(e.g. SPF information).</para>
|
||||
|
||||
<screenshot>
|
||||
<mediaobject>
|
||||
|
@ -4317,8 +4341,8 @@ Run slapindex to rebuild the index.
|
|||
|
||||
<para><emphasis role="bold">Services (SRV)</emphasis></para>
|
||||
|
||||
<para>Service records can be used to specify which servers provide common
|
||||
services such as LDAP. Please note that the host name must be
|
||||
<para>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).</para>
|
||||
|
||||
<literallayout>
|
||||
|
@ -4349,8 +4373,8 @@ Run slapindex to rebuild the index.
|
|||
|
||||
<para><emphasis role="bold">File upload</emphasis></para>
|
||||
|
||||
<para>You can upload complete DNS zones via LAM's file upload. Here is an
|
||||
example for a zone file and the corresponding CSV file.</para>
|
||||
<para>You can upload complete DNS zones via LAM's file upload. Here is
|
||||
an example for a zone file and the corresponding CSV file.</para>
|
||||
|
||||
<table>
|
||||
<title>Zone file</title>
|
||||
|
@ -4454,9 +4478,9 @@ Run slapindex to rebuild the index.
|
|||
<para>Please check that you have an existing zone entry that can be used
|
||||
for the file upload. See above to create a new zone.</para>
|
||||
|
||||
<para>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.</para>
|
||||
<para>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.</para>
|
||||
|
||||
<para>In this example we assume that the following zone extry
|
||||
exists:</para>
|
||||
|
@ -4472,6 +4496,25 @@ objectclass: top
|
|||
url="resources/bindUpload.csv">bindUpload.csv</ulink></para>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<title>XFR entries</title>
|
||||
|
||||
<para>You can manage the XFR entries in the second tab that you
|
||||
configured before.</para>
|
||||
|
||||
<screenshot>
|
||||
<graphic fileref="images/mod_bind16.png"/>
|
||||
</screenshot>
|
||||
|
||||
<para>For each XFR entry you can set a record ID and the IP
|
||||
address.</para>
|
||||
|
||||
<screenshot>
|
||||
<graphic fileref="images/mod_bind15.png"/>
|
||||
</screenshot>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<title>Aliases (LAM Pro)</title>
|
||||
|
||||
|
|
Binary file not shown.
After Width: | Height: | Size: 43 KiB |
Binary file not shown.
After Width: | Height: | Size: 37 KiB |
Binary file not shown.
After Width: | Height: | Size: 25 KiB |
Binary file not shown.
After Width: | Height: | Size: 45 KiB |
Loading…
Reference in New Issue