Network binding order is checked on the user's dns domain, not the machine domain by spaghettidba

The Network Binding Order rule check in the cluster setup has a serious logic flaw: the domain network is detected using the user's dns domain and not the machine's dns domain.
That means that whenever you run the setup on a computer on a trusted domain, you get false positives for this rule.
Here's an example from the Detail.txt (domain names changed for privacy reasons):

2013-01-03 12:03:59 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.NetworkBindingFacet
2013-01-03 12:03:59 Slp: NetworkBindingFacet: Looking up network binding order.
2013-01-03 12:03:59 Slp: NetworkBindingFacet: Network: 'Domain Team' Device: '\Device\{C002FF0D-9EF2-46F7-A651-FA1DE4653D8C}' Domain: 'trusted.domain.name' Adapter Id: '{C002FF0D-9EF2-46F7-A651-FA1DE4653D8C}'
2013-01-03 12:03:59 Slp: NetworkBindingFacet: Network: 'Cluster Team' Device: '\Device\{60E7366B-37DD-4BCB-82A7-35B22DCE9F55}' Domain: '' Adapter Id: '{60E7366B-37DD-4BCB-82A7-35B22DCE9F55}'
2013-01-03 12:03:59 Slp: NetworkBindingFacet: Network: 'Storage Team' Device: '\Device\{CCE22F0E-C2E0-42AB-9590-D336D1ED391D}' Domain: '' Adapter Id: '{CCE22F0E-C2E0-42AB-9590-D336D1ED391D}'
2013-01-03 12:03:59 Slp: IsDomainInCorrectBindOrder: The top network interface 'Domain Team' is bound to domain 'trusted.domain.name' and the current domain is 'user.domain.name'.

Running the setup again as a users in the trusted domain generates no warnings.