SIM picks wrong DNS names

[Kevin Kelling]

I have noticed that trusts cannot be established with servers which have a different Windows name than what SIM knows.

For example a Windows node might be known as SERVERx in the Active Directory. However, in DNS it is known as a different name (provided by a static entry) in order to accomodate web sites and other applications. The DNS names we assign are in a different DNS zone (non-AD) and will always be the first response to a reverse lookup query. This is intentional.

I have deleted and re-added nodes several times using manual menthods and hosts files.

No matter what I do, SIM grabs the name in DNS instead of the Windows host name, prohibiting the possibility of establishing a trust and being able to manage the node.

How does one override this behavior (of grabbing the results of a reverse DNS lookup) instead of using the name provided or the native Windows host name.

We have about two dozen servers that cannot be managed by SIM because of this issue.

Thanks!

[Joel Rubenstein · Accepted solution]

SIM actually references the file C:\WINDOWS\system32\drivers\etc\hosts before checking DNS.

You can use the command

mxgethostname -n "ip address" to see the name that will be used by SIM.

[Kevin Kelling]

Actually thats a feature of Windows if I am not mistaken (looks at hosts file first).

the solution was too obvious for me to consider :^)

Thanks!