Question : PTR Records on Internal DNS

Hello,

We host our own internal and external DNS.  On the internal side, my reverse lookup zone is a mess.  I have PTR records for the same IP pointing to various machines and vice versa.

Question 1:  where or what creates the PTR record?  Does doing a /flushdns and /registerdns all records for the host its run on?

Question 2:  why do i have some records with host name machinename. and others have machinename.domain.com?

Here are some examples of what i have

10.1.1.25   Pointer(PTR)    host1.domain.com
10.1.1.25   Pointer(PTR)    host2.
10.1.1.25   Pointer(PTR)    host2.domain.com
10.1.1.25   Pointer(PTR)    host3.domain.com

and on the flip side

10.1.1.96   Pointer(PTR)    host12.domain.com
10.1.1.45   Pointer(PTR)    host12.domain.com
10.1.1.12   Pointer(PTR)    host12

how do i clean this up?  I was thinking I can use a login script that would run ipconfig /flushdns and ipconfig /registerdns but I tested this on a few machines and it's not cleaning up the records.

Thanks

Answer : PTR Records on Internal DNS

You never answered the question I asked you...

If zones are a mess you should set Aging limits. Scavenging is only half of the process, you can enable it all you want, but it won't do anything at all unless you actually set the aging limits. Normally these should when added together equal your DHCP Lease time. That is, if your DHCP lease is 10 days then 5 days for No-Refresh and 5 days for Refresh would be appropriate.

Chris