https://community.hpe.com/t5/server-management-systems/sim-picks-wrong-dns-names/m-p/3340075#M4542 I have noticed that trusts cannot be established with servers which have a different Windows name than what SIM knows.<BR /><BR />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.<BR /><BR />I have deleted and re-added nodes several times using manual menthods and hosts files. <BR /><BR />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.<BR /><BR />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.<BR /><BR />We have about two dozen servers that cannot be managed by SIM because of this issue.<BR /><BR />Thanks! Fri, 23 Jul 2004 15:14:33 GMT Kevin Kelling 2004-07-23T15:14:33Z https://community.hpe.com/t5/server-management-systems/sim-picks-wrong-dns-names/m-p/3340075#M4542 I have noticed that trusts cannot be established with servers which have a different Windows name than what SIM knows.<BR /><BR />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.<BR /><BR />I have deleted and re-added nodes several times using manual menthods and hosts files. <BR /><BR />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.<BR /><BR />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.<BR /><BR />We have about two dozen servers that cannot be managed by SIM because of this issue.<BR /><BR />Thanks! Fri, 23 Jul 2004 15:14:33 GMT https://community.hpe.com/t5/server-management-systems/sim-picks-wrong-dns-names/m-p/3340075#M4542 Kevin Kelling 2004-07-23T15:14:33Z https://community.hpe.com/t5/server-management-systems/sim-picks-wrong-dns-names/m-p/3340076#M4543 SIM actually references the file C:\WINDOWS\system32\drivers\etc\hosts before checking DNS. <BR /><BR />You can use the command <BR /><BR />mxgethostname -n "ip address" to see the name that will be used by SIM. Fri, 23 Jul 2004 15:53:18 GMT https://community.hpe.com/t5/server-management-systems/sim-picks-wrong-dns-names/m-p/3340076#M4543 Joel Rubenstein 2004-07-23T15:53:18Z https://community.hpe.com/t5/server-management-systems/sim-picks-wrong-dns-names/m-p/3340077#M4544 Actually thats a feature of Windows if I am not mistaken (looks at hosts file first).<BR /><BR />the solution was too obvious for me to consider :^)<BR /><BR />Thanks! Fri, 23 Jul 2004 16:00:57 GMT https://community.hpe.com/t5/server-management-systems/sim-picks-wrong-dns-names/m-p/3340077#M4544 Kevin Kelling 2004-07-23T16:00:57Z