For some other "user" perspective, let me offer this has been brought up from time to time and I haven't seen a proposed resolution that completely fixes it for me, either.
When I've run into this issue (and it has been many times over the last couple of years), this is the process I used to resolve it:
-
Create an entry for the problem device listing in Local DNS/DNS Records (enter the desired hostname and the IP address that is currently assigned to your client device)
-
Go to Tools/Network and locate the entry for the device you are "correcting"; delete this entry
-
Wait a minute or two (assuming the device is active on the LAN), then check Tools/Network again for the problem device. Keep checking until it shows up again; when it appears, it should have the information you entered above in the Local DNS/DNS Records list.
-
Upon confirmation of the info in the prior step, go to Local DNS/DNS Records and delete the entry you created in the first step.
This process has enable me to fix problem entries and have the changes "stick" indefinitely, even if the devices IP address later changes via DHCP assignment.
Hopefully that helps work around this issue for those who might encounter it.