This is because the client will not update itself due to the current record in DNS is beyond the lease period.
This happens even though DHCP registered the record.
and name was resolved.3- Edited blablabla1 to blablabla2 and when submitted the ack popped then override and dhcp was updated but not dns the old record persist and the new one was not created.
I originally posted this in Linux Questions without much luck, so I'll try here.
Please note, this tool only works when existing PTRs are associated with the Server or VLAN.
If no PTRs exist, there will be no details listed and attempts to update will result in an error.
When a client shuts down, and later returns past the lease time, it may get a different IP address.
This tool allows a user to enter a portion of a PTR or the full PTR in the Search field and replace each occurrence within corresponding PTRs with the desired information.
For reverse DNS you will have to setup your reverse DNS domain.
This is a special domain that ends with “in-addr.arpa”.
Even foreman proxy logs won't show any nsupdate for the new hostname. Cannot reproduce the issue -- A and PTR records are being created and updated correctly.
Can you verify that dns updates have been configured correctly?