How to configure isc-dhcpd-server to update reverse zone without client pre configuration?

[Vladimir Skubriev]

How to configure isc-dhcpd-server to update reverse zone without client pre
configuration?

I'm trying to set up isc-dhcpd-server from ubuntu 16.04 (4.3.3-5ubuntu12)
to configuring heterogeneous network with ubuntu, windows, macos, other ip
devices.

I'm already setuped bind to store ip address configuration of statically
configured hosts in dns. My internal zone already has an A records like:

client.example.lab a 900 192.168.1.10
server.example.lab a 900 192.168.1.11

Also I have statically defined hosts on dhcpd.conf like:

host client {
hardware ethernet: 08:00:27:d8:78:e5
fixed-address client;
}

I don't want to update A records in my internal zone example.lab
dynamically. Because this setup requires sustained attention to clean up
zones because of update errors like 'YXDOMAIN, NXRRSET etc'

I want to update dynamically only reverse zone of my internal subnet
192.168.1.0/24

So I configured the dhcpd server as follows:

ddns-updates on;
do-forward-updates off;

The documentation states that:

do-forward-updates flag;

...

If this statement is used to disable forward updates, the DHCP server will
never attempt to update the client's A record, and will only ever attempt
to update the client's PTR record if the client supplies an FQDN that
should be placed in the PTR record using the fqdn option.

I tried to setup this option manually on ubuntu in /etc/dhcp/dhclient.conf
as follows:

send fqdn.fqdn = "client.example.lab"

In this case dhcpd server succesfully updates reverse PTR zone with this
fqdn name. Also it is point the obtained ip to this fqdn name.

But this workflow assumes that I need to configure each client in the net.

Is there another way to configure isc-dhcp-server for retrive fqdn.fqdn
from the server itself, without client pre-configuration?

Is it is impossible now with isc-dhcp-server ?



--
Faithfully yours,

CVision Lab System Administrator
Vladimir Skubriev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20160518/cc4f798f/attachment.html>