Multizone nodes are currently identified with a key (that gets generated?) and by the zone name. The auditor dictionary that contains these nodes uses the key, so it isn't possible to look up connections directly (particularly when distribution links are involved). This needs to be straightened out both here and in the epJSON.