tor uses getaddrinfo even if DisableNetwork is set
If DisableNetwork is set, but tor is passed a textual (?) address in a
*Port config line, it uses
getaddrinfo to lookup the address. This can access the network and cause config parsing to hang. (See legacy/trac#16366 (moved).)
The documentation for DisableNetwork could be clearer about this - that tor will make certain network-related calls as part of its config process, even if DisableNetwork is set.
If the config uses names that need to be looked up using the network, this also means the external network needs to be up for config parsing to succeed. (Which seems like an unexpected dependency.)
So DisableNetwork may not be able to be used as described (implied?) - for a controller to setup the config while the network is down, then re-enable tor networking when the network comes up.