Your problem, as stated, is that the name→address DNS lookup for your computer results in a different IP address to the one that the computer actually has. This has nothing to do with
PTR resource records, which are not involved in name→address DNS lookups. (They are used for address→name lookups.) Cleaning up your
PTR records won't do a thing for your stated problem.
What will fix your problem is finding out why the name→address DNS lookups aren't correct. Since you are using DHCP, your DNS database should be being dynamically updated with the name→address maps as the DHCP server hands out leases. For best results, one configures one's DHCP server to talk to the DNS server directly, the former sending the updates to the latter as leases are granted and renewed. Only the DHCP server needs to security permissions to modify the DNS data through dynamic update.
But some people have their DHCP clients do this. In which case one can run into various permissions problems, such as DHCP clients not having appropriate update permissions, or not being able to update records in the database that they don't have the access rights to, or being able to hijack special-use domain names that they shouldn't be able to claim. There are also various problems with domain name suffixes that can raise their heads.
So find out whether your DHCP server or your DHCP clients are sending the updates to the (content) DNS server. Ensure that the access controls let whichever is performing the updates do so, ensure that the server is recieving the update traffic, ensure that the appropriate parts of the namespace are updatable, ensure that all of your advertized content DNS servers can actually update the DNS database, and ensure that the updates are ending up with the correct domain names.