Marc Chametzky wrote ... $ MCR NCP SET CIRCUIT TCP-x-y STATE OFF $ MULTINET SET/DECNET/REMOTE=a.b.c.d/CONNECT $ MCR NCP SET CIRCUIT TCP-x-y STATE ON Yes, you could do this. The only part missing is something that queries DNS to determine the actual IP address. That's do-able too, but not quite as trivial. One could also reflect this change in MULTINET:DECNET-CIRCUITS.COM to save the change for later (best done indirectly through MULTINET CONFIGURE/DECNET). You'd have to; otherwise the next time you rebooted the new IPs would go away. Does DECnet routing require explicitly created paths to avoid routing loops, or can one have multiple parallel connections and have DECnet manage the routing dynamically? The short answer is that this is what circuit costs are for - in the event of multiple paths, DECnet will pick the least cost route to the destination. Having multiple paths from node A to node B isn't supposed to be a problem. Bob