this is an interesting case actually... this is `nsqlookupd` sending back information to the `nsqd` that just identified itself so that the `nsqd` can subsequently query this `nsqlookupd` via HTTP.  Specifically, `nsqd` needs to know the HTTP port that its configured `nsqlookupd` are listening on... this accomplishes that exchange.

Unfortunately, that means `nsqlookupd` needs the same `--broadcast-address` flag added so that here, it can pass along **it's** broadcast address because I imagine in your environment you'll have the same name resolution issue that started this whole changeset in the first place on the `nsqd` side.