On Feb 12,  0:59, Colin Wood wrote:
> Subject: Re: Help setting up access to name server...
> create/edit /etc/resolv.conf to be the following:
>
> ;configure domain name service
> ;the following should be a comma-separated list of domains to search
> search alaska.edu
> nameserver 137.229.16.20
>
>
> That should be about all it takes, except for the fact that named needs
> to be turned on in /etc/netstart.  Once you have your resolv.conf written
> out, you can kill -HUP named to make it recognize any changes you make.

named shouldn't be running with that resolv.conf. There are possible
performance advantages in running named, in that it could be used as a local
cache, but if you wanted to do that, you'd want the nameserver line to be
127.0.0.1, localhost so that you queried your nameserver, otherwise it would
never be used.

Then, you would probably want a forwarders line in named.boot to tell your
running named to ask the real name server for the things you didn't already
know (but then again, maybe you wouldn't :)

The simple client configuration is to have the resolv.conf as above, but not
running named.

Bernard.