Keith Keller wrote:
>
> NIS will look *up* hosts if told to, but that's not the OP's problem.
> His problem is that his NIS server is not using the correct
> nisdomainname. Modifying resolv.conf will not address this problem.
>
Actually, I consider the real problem to be the "Not a valid domain"
error. I believe the name issue to be secondary. i.e. not the primary
problem. I was trying to change the name because it was originally the
same as the DNS name, which it should not be. However, my understanding
is that that should not cause it to fail.

Both problems look solved now.

> (In any case, IIRC resolv.conf won't actually affect NIS name lookups,
> since it's used by the BIND resolver libraries. You configure NIS host
> maps completely separate from resolv.conf. And at any rate, the OP
> doesn't even need an NIS host map!)
>
I started looking at resolv.conf because the "dig" program would not
resolve "enterprise". It was making my DNS go out to the root servers
of the internet looking for a top-level domain called "enterprise",
which, naturally there isn't one.

nslookup does resolve "enterprise" into "enterprise.mrj". Apparently,
dig does not pay attention to domain/search directives in resolv.conf,
but nslookup does.

So the resolv,conf was a red herring on my part. I was also messing
with it due to the unreliability of my ISP's DNS (which is a big part of
why I run my own!).

Mark