On 2005-02-18, E. Charters <echarters@sympatico.ca> wrote:
>
[ > I wrote: (please don't snip attributions!) ]
[ >> E. Charters <echarters@sympatico.ca> wrote: ]

>>>you could try a "domain" directive in resolv.conf
>>
>> resolv.conf applies only to DNS, *not* to NIS!
>
> # no, that is not how it works. NIS will look for hosts in
> DNS and hosts files too. It uses resolv.conf. At least it
> does in some systems.

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.

(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!)

> You could puts "nis" in your hosts.conf file under order

Neither will this address the OP's problem.

> Also perhaps /etc/defaultdomain should be set.

The OP said he already did this! In addition, you snipped the part
where I wrote that /etc/defaultdomain is *only* used by rc.yp, and not
by any of the actual yp* binaries. Only nisdomainname actually sets the
NIS domain name (and nisdomainname is called by rc.yp).

--keith

--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom
see X- headers for PGP signature information