On 09/29/2016 04:45 PM, Darcy Kevin (FCA) wrote: > Yeah, sure, just run it with your own special config file (with -c); in that > config file, set the listen-on to an unprivileged port, and make sure all of > the pathnames (including implicit pathnames like the pid-file) are to > files/directories to which the unprivileged user has read and (where > necessary) write access. > > As a sanity check, I just fired up an instance on a Red Hat box, as an > unprivileged user, listening on port 12345. It's a caching-only config, with > our own internal-root hints, and it's resolving (internal) names just fine. > > > - Kevin
How did you get your code to look at that instance:port rather than the one dictated by /etc/resolv.conf or a local server on port 53? ---------------------------------------------------------------------------- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
