I’m running isc dhcp 4.2.5 on Centos 7, and named 9.9.4.
Our computers all know their names, which are their inventory barcodes ex, “cs00123”, “hr45678”
While simple machines like printers or basic computers have no problems registering with DHCP, and having their information entered in named, we are seeing that the computers that are connected to the local domain server are providing client names of “cs00123.Health1.HCOM.Health.State.NY.US.”.
This does not seem to be an issue for DHCP, but we are registering DNS Reverse records of cs00123.health1.hcom.health.state.ny.us and not registering forward records at all.
I’d thought that I could re-write the address by specifying the following in the subnet
ddns-hostname = substring (option host-name, 0, 7);
ddns-domainname = “esp22.wadsworth.org”;
again, this works fine for printers, and non-domain computers.
We would like the domain member computers to have forward and reverse records of
10.57.36.22 in a cs00123.wadsworth.org.
10.57.36.22 in ptr cs00123.wadsworth.org.
And not healt1.hcom….us
I will include the full zone and subnet info.
Any help to debug/fix this issue would be appreciated.
zone esp22.wadsworth.org. {
primary 199.184.30.15;
key dhcpupdate;
}
#### default_vlan at ESP, Vlan 22
subnet 10.57.36.0 netmask 255.255.252.0 {
authoritative;
#use-host-decl-names on;
option routers 10.57.36.1;
ddns-hostname = substring (option host-name, 0, 7);
ddns-domainname = "esp22.wadsworth.org";
ddns-rev-domainname "in-addr.arpa.";
option domain-name-servers 199.184.30.15, admin.wadsworth.org, bionsc.wadsworth.org, ldap1.wadsworth.org;
pool {
range 10.57.36.10 10.57.39.254;
allow unknown-clients;
allow known-clients;
# deny dynamic bootp clients;
option domain-name-servers 199.184.30.15, 199.184.30.91, admin.wadsworth.org, bionsc.wadsworth.org, ldap1.wadsworth.org;
}
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150210/a827b407/attachment.html>