In an earlier post, I described an approach for resolving names when the connection specific DNS suffix did not match the Active Directory domain name. Recently, I realized that there is a much simpler solution. The Default ComputeNode Template which is created when you run through the Node Template Creation Wizard contains a step for joining the AD domain, but unless you edit the template, the field for specifying the AD domain name is blank. If that field is blank, the compute nodes will use the primary DNS suffix of the head node as the name of the AD domain they attempt to join, and if there is no such domain, that step will fail. So, the solution is simply to edit the Node Template and add the AD Domain name to that field.