This surfaced as a problem with npm install, npm/npm#7508

The bug seems to have been introduced in the 0.11 (now 0.12) node line, which io.js inherits.

I found some evidence that FreeBSD returns different error codes than Linux (EAI_FAIL instead of EAI_NONAME) on certain conditions, see this thread from the samba bug tracker: https://bugzilla.samba.org/attachment.cgi?id=8563&action=edit

I don't have a FreeBSD box to test this on. @msimerson has the FreeBSD box with the unusual setup (only using loopback network addresses)