Dhcp lease not updating dns Sexchat captures
My question is concerning dynamic DNS updates by DHCP.I have a Cent OS 6.4 server which is both a DNS server and DHCP server for the internal network. The server also runs Samba4 AD which interacts with BIND using the DLZ plugin.I have also tried entering a name in the "Client ID" (normally blank) of the Wi-Fi settings.This shows up in the DHCP leases file asbut again does not solve the problem.I am beginning to suspect that the problem lies in the client side, but I don't understand why because I believe the DHCP server should just update the DNS server regardless of any client settings or behaviour. Is it possible that you could compare your and files against what I have listed above and tell me if they match or if I'm missing something? Is it possible that you could compare your and files against what I have listed above and tell me if they match or if I'm missing something?But, if the problem is client side, with a cut-down OS like IOS or Android I don't know if I could change its behaviour. Also, does your dhcpd.leases file have the "set ddns...." lines for the i Phone entries? Also, does your dhcpd.leases file have the "set ddns...." lines for the i Phone entries? The entries have expired from the dhcp tables, or perhaps were put in place before a transition -- I don't know why the dhcp server has not remove the corresponding dns entries.With Samba4 AD the clients will automatically update the DNS forward zone.Active Directory requires DNS updates to be Kerberos signed, so it only works for the Windows PCs joined to the example.local AD domain.
The DHCP and DNS configuration was modified slightly with relevant changes as shown below.dhcpd.conf: The reverse zone file was moved to /var/named/dynamic so permissions allow it to be updated. The 'PTR' records are added to the reverse zone file with the IP addresses allocated by DHCP.
Are you sure they were added by DHCP or could they have been added manually?
As for the settings in your file, both 'do-forward-updates' and 'ddns-updates' are enabled by default according to the documentation.
I have read posts on the Internet from people with mixed environments reporting that dynamic DNS works for their Windows clients but not Linux clients.
The solution appeared to involve adjustment of the on the Linux clients and related to the client reporting a FQDN.