Created Unassigned: {domain} token doesn't resolve to domain name. [2533]

I'v touched this issue in [issue #2532](https://ldapcp.codeplex.com/workitem/2532)
Basically Active Directory domain int.domain1.local ``` name ``` attribute is ```int``` and ``` nETBIOSname ``` attribute is ```domain1 ``` and that results in populating {domain} token with ``` int ``` rather than ```domain1```. That results in finding and resolving users prepended with int\ and not domain1\.

This raises me a question if LDAPCP correctly populates the {domain} token. If i lookup msDS-PrincipalName attribute, it is constructed of __[nETBIOSName (from domain)]\\[sAMAccountName (from group)]__ : https://msdn.microsoft.com/en-us/library/cc223404.aspx?f=255&MSPPError=-2147217396

If i open Active Directory Users and Computers, it shows me "Domain name (pre-Windows 2000)" is __domain1__ and not __int__

Should LDAPCP use nETBIOSName rather than name attribute within __SearchObjectsInLDAP__?

I haven't found why name and nETBIOSName is different. But the nETBIOSName can be used to identify a domain:
> (3) A domain name (2) or a NetBIOS name that identifies a domain. https://msdn.microsoft.com/en-us/library/cc232152.aspx