Bind DLZ (LAM Pro)
Prev | Chapter 4. Managing entries in your LDAP directory | Next

## Bind DLZ (LAM Pro)

Bind DLZ is an extension to the DNS server Bind that allows to store DNS entries inside LDAP. Please install the Bind DLZ schema file on your LDAP server. It is part of the DLZ patch.

Configuration

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.

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.

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.

Zone management

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.

DNS entries

LAM supports the following DNS record types:

- SOA: authoritative information

- 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

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)

LAM will automatically set the correct type (A/AAAA) depending if you enter an IPv4 or IPv6 address.

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.

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.

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.

Text records (TXT)

Text records can be added to store a description or other data (e.g. SPF information).

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).

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.

Port: The port number that is used for your service.

Server: DNS name where service can be reached (with dot at the end).

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.

Table 4.2. Zone file

@ | IN | SOA | ns1.example.com admin.ns1.example.com (1 360000 3600 3600000 370000)
| IN | NS | ns1.example.com.
| IN | NS | ns2.example.com.
| IN | MX | 10 mail1.example.com
| IN | MX | 20 mail2.example.com
foo | IN | A | 123.123.123.100
foo2 | IN | CNAME | foo.example.com
bar | IN | A | 123.123.123.101
| IN | AAAA | 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.

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:

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

Prev | Up | Next
DHCP | Home | Aliases (LAM Pro)