DragonFly BSD
DragonFly users List (threaded) for 2005-12
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: NIS setup

From: Oliver Fromme <check+irljcu00rsffvgcy@xxxxxxxxxx>
Date: 16 Dec 2005 15:51:27 GMT

Chuck Tuffli <ctuffli@xxxxxxxxx> wrote:
 > nis_client_enable="YES"
 > nisdomainname="sierra"
 > nis_client_flags="-S sierra,earth,mercury"
 > sldev12-l# ypwhich
 > ypwhich: can't yp_bind: reason: Domain not bound
 > I doubled checked and both ypbind and portmap are running. In trying
 > random things found via google, the following sequence seems to fix(?)
 > the problem:
 > # killall ypbind
 > # ypbind -ypsetme
 > # ypset sierra
 > where 'sierra' is the NIS domain name. Does this help explain what is
 > happening? Tnx again.

It looks like the ypbind command is ignoring the -S option,
which happens when the hostnames (at least one of them)
cannot be resolved.

When you use the (insecure!) ypset command, then ypbind
searches for the servers itself by broadcasting queries
on the local network.  No hostname resolving is required
in that case.

To fix the problem, be sure that the hostnames in the -S
option are resolvable.  Try adding the domain name.  Note
that using numeric IP addresses does not work, contrary
to the manual page.  If everything else fails, add the
host names to /etc/hosts.

Another possibility is to setup the client machines as
slave servers.  In that case, ypbind only needs to bind
to localhost, which should always succeed.

Best regards

Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd

Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]