Bad FQDN: ";; connection timed out; no servers could be reached.master"

[Jeroen T. Vermeulen]

Lord_Set reports seeing a node with this strange FQDN:

;; connection timed out; no servers could be reached.master

That looks like the output from a failed "dig" invocation, combined with the nodegroup name. The dig tool has the annoying habit of printing its errors to stdout instead of stderr.

The enlist_userdata invokes dig without checking for errors:

   ip=$(ifconfig eth0 | awk '$1 == "inet" { sub("addr:","",$2); print $2; }') &&
     [ -n "${ip}" ] && host=$(dig +short -x $ip) && host=${host%.}
   # load ipmi modules
   load_modules

—which looks like it would explain the problem.