A common scenario is to have the Windows HPC Server 2008 Private Network DNS on the head node of the cluster. Because the HPC Pack normally manages name resolution for the private network via Hosts files it propagates to all nodes, we do not normally set the private network interfaces to register with the DNS on the head node.
I often find that I want to have other servers such as file servers or non-Windows OS servers located on the private network. These servers need to have all the names on the private network correctly resolved for them.
To get the behavior I desire from the head node private DNS is very simple, but not documented as widely as we’d like. Thus, this post seems like a good start at getting the trick documented.
On the head node go to Start->Microsoft HPC Pack->HPC PowerShell and right click selecting Run As Administrator. At the prompt enter the following:
PS C:\Windows\System32> Set-HpcNetwork -PrivateDnsRegistrationType WithConnectionDnsSuffix
This executes silently. I noticed that not many new Host(A) records appeared in my DNS console. I was told, “Be patient.” Instead, I just rebooted all nodes, including the non-Windows OS node Node-08.
Voila! I got my Host(A) records for everything.
I'm working with an HPC cluster (network topology 1) with a seperate DNS server (not part of the head node).
Can I assume that this wonderful little trick will work with a scenario where the DNS Server is independant of the head node?
Does this setting have any other affects on the cluster beyond just 'turning on' allowing DNS registration?
we have twp head nodes. I am confused about the syntax of this command. Can you give an example where say ServerA has a private IP of 192.168.1.1 and it needs to be registered on the head node Hosts file . How would i type this command? Secondly, in a clustered head node situation, would I need to run it just on a single head node or both?
Head on over to social.microsoft.com/.../windowshpc to ask questions / provide feedback / join the Windows HPC community!