bind10 running as user bind fails to start resolver service

[Spain, Dr. Jeffry A.]

> Right now the auth and resolver need to start as root (in case they need to bind sockets to a privilege port, which is normally the case) and then internally change their user.  For the obviously reason it won't work if you do this from a running BIND10 system.

> We're going to solve this inconvenience by introducing a separate "socket creator" process, which will be the only process that needs the root privilege.  For now, please shutdown the entire system and start it from the scratch with the new configuration (which, for example, enables the resolver server).

Thanks. I will try that after first finishing the initialization script and report the results. Jeff.