system collection using ptr dns records for some client names and netbios names for other.

HI,
 
Strange problem I am seeing.  We are runnning sccm 2007 over windows 2008 R2 fully patched.  For sometime, I have noticed some client's with the sccm client installed will be labeled by their PTR record name rather than their netbios name in the all systems collection.  The REV zone for our simple subnet is running on a linux/bind server.  the dhcp server is also running on linux.  When I look at the properties of the sccm client object's properties tab in the all system's collection, the netbios name value is always the PTR record name.....even if the name in the collection is the netbios name.  I am seeing about 50% of the clients having the ptr name listed in the console. 
 
Does anyone have any insight why the console would name the sccm client the PTR name rather than the netbios name?  all system's are running xp sp3 with most updates and patches installed. 
 
thanks
 

No real idea, but perhaps a way to look for a pattern.
On a box that has the PTR vs. one that does not, in the console right-click and look at Properties.  In there will be all of the last Discovery that have run for that particular box.
Perhaps you'll find that the ones that display the PTR record is because "network discovery" was the last discovery that reported vs. Heartbeat (or something, I'm just making this up).  Hopefully you'll find a pattern and then be able to go forward from there with a plan.
 
Edit: you know about this Usergroup?  http://mnscug.org/

thanks for the reply,
 
the only pattern I see right now is this:  the netbios name value in the computer's object properties tab always points to the PTR name.  I am looking into name resolution precedence for the server and then some clients.  I thought MS clients servers always had host/wins/dns/brod as the name resolution.
 
thanks
 

What I meant was, the netbiosname property could be 'discovered' from one of several of the potential discovery methods.
So, perhaps heartbeat is reporting correctly, but perhaps you have network discovery enabled, and perhaps network discovery is reporting the PTR netbios name.
That is why I asked you to look at properties of one reporting "correctly" and one not.  perhaps you can see if the one reporting correctly, the last discovery that ran for it was heartbeat.  But for the other, the one with the PTR, the last discovery for it was network discovery.
Again, I'm 100%, absolutely 100% whistling in the dark. 

Hello,
 
Last Friday, I disabled the network discovery in sccm.  Heart beat is still enabled.  the other methods for discovery are the active directory options.  After disabling the network discovery method, the sccm started to reflect the clients ms netbios name rather than the PTR record name.  The changes started to occur the next day.    
 
what I can conclude is this:  the sccm server will resolve the netbios names to either the PTR lookup or to the netbios lookup....depending on what lookup occurs first.  I had thought that once the client was installed and active in the site's domain, at least the netbios name would reflect the true value...a netbios name and not the PTR lookup.  Interesting.....
 
Thanks for your help