Conflict of details from AD scan and Network scan

Appreciate this MAY be related to my other query re maintaining names of assets in scans, but maybe no so as not to confuse I'l open a new topic on it.

ServerX is in AD and has been detected and is updated each time a AD scan runs.
This server has two IP address, the primary is assigned to the machine name on teh network ( 192.168.1.1 for instance )
The other address is also bound to the same NIC in the server but exposed in DNS with name www.name1.com ( 192.168.1.2 for instance )

The network runs a mix of Windows and other servers, so I have run a network scan on the 192.168.1.x range and that has populated www.name1.com into the asset database, but with no details assigned. I have changed the login credintials for www.name1.com to be the domain login, and the scan picks up cleanly BUT finds nothing to populate.
So I'm left with SERVERX correctly identified and a real asset and www.name1.com as a network detected asset that doesn't know that it is really ServerX.

How can I resolve this situation so I don't have a duplicate?
Regards,
Andy

SD+ Enterprise
Build 7004
MS SQL 2005