1821413 Members
2444 Online
109633 Solutions
New Discussion

NIS domain is not bound

 
Ravi kumar raju
Advisor

NIS domain is not bound


HI
We are facing NIS bind issue. My NIS server is in 16 subnet and my Nis clients (hpux) are in 15 subnet. We don’t have Nis slave. How to fix this issue. What are the configurations I have to check in client side?

error:
client# ypwhich
NIS domain is not bound.


Thanks,
Ravi kumar.R

11 REPLIES 11
Steven E. Protter
Exalted Contributor

Re: NIS domain is not bound

Shalom,

Check that the service for the NIS client is enabled in /etc/rc.config.d/namesvers

See that the configuration make sense and the master NIS servers are on the network and accepting connections.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Peter Nikitka
Honored Contributor

Re: NIS domain is not bound

Hi,

you probably have to configure YPSET-information, because the usual broadcast mechanism won't span subnets.
For testing purposes you can start
ypclient -ypsetme
and then call
ypset

If that works, add that information to the apropriate variables in
/etc/rc.config.d/namesvers

mfG Peter

The Universe is a pretty big place, it's bigger than anything anyone has ever dreamed of before. So if it's just us, seems like an awful waste of space, right? Jodie Foster in "Contact"
Safarali
Valued Contributor

Re: NIS domain is not bound

Hi Ravi Kumar
Please provide the output of
/etc/rc.config.d/namesvers

Regards
Safar
Ravi kumar raju
Advisor

Re: NIS domain is not bound

HI Safar,

Please find the /etc/rc.config.d/namesvrs output configuration,All 20 NIS client are facing same problem.


# cat /etc/rc.config.d/namesvrs
unset UNIX95
PRE_U95=true;export PRE_U95;

##############################################
# named (BIND) configuration. See named(1m). #
##############################################
#
# Name server using the Domain Name System (DNS) protocol (RFC 1034/1035)
#
# @(#)B11.23_LR
#
# NAMED: Set to 1 to start nameserver daemon.
# NAMED_ARGS: Arguments to the nameserver daemon
#
# Configuration of a named file (e.g. /etc/named.conf) is needed for
# successful operation of the name server.
#
NAMED=0
NAMED_ARGS=""


##########################################################
# NIS (YP) configuration. See domainname(1), ypserv(1m) #
##########################################################
#
# Name server using Network Information Service protocol (Sun's ONC)
#
# NIS_MASTER_SERVER: 1 if this node is the master NIS server, 0 if not.
# NIS_SLAVE_SERVER: 1 if this node is a slave NIS server, 0 if not.
# NIS_CLIENT: 1 if this node is a NIS client, 0 if not.
# NISPLUS_SERVER: 1 if this node is a NIS+ server, 0 if not.
# NISPLUS_CLIENT: 1 if this node is a NIS+ client, 0 if not.
# EMULYP: -Y to have rpc.nisd support YP clients.
# NISDOMAIN: the NIS domain name (see domainname(1)).
# NISDOMAIN_ERR: ???
# MAX_NISCHECKS= max number of bind attempts the NIS client will make
# YPSERV_OPTIONS command line options for ypserv
# YPBIND_OPTIONS command line options for ypbind
# YPPASSWDD_OPTIONS command line options for yppasswdd
# KEYSERV_OPTIONS command line options for keyserv
# YPUPDATED_OPTIONS command line options for ypupdated
# YPXFRD_OPTIONS command line options for ypxfrd
# RPC_NISD_OPTIONS command line options for rpc.nisd
# NIS_CACHEMGR_OPTIONS command line options for nis_cachemgr
# YPSET_ADDR IP addr or name of NIS server. Must set YPBIND_OPTIONS
# to "-ypset"
# LONGNAMES_OPTIONS
# SHORTNAMES_OPTIONS
#
# Note: - NIS_MASTER_SERVER and NIS_SLAVE_SERVER are mutually exclusive,
# i.e., only one, not both, should be set if either is set.
# - All NIS servers must also be NIS clients, so if you set either
# NIS_MASTER_SERVER or NIS_SLAVE_SERVER to 1, you should set
# NIS_CLIENT to 1, too.
# - Refer to NFS administration manual and ypinit(1M) for the
# steps required to create NIS servers.
#
# MAX_NISCHECKS
# The maximum number of bind attempts the
# NIS client will make for a NIS server to be
# available before shuting down NIS and
# booting without it. This value should
# not be less than 2.
#
NIS_MASTER_SERVER=0
NIS_SLAVE_SERVER=0
NIS_CLIENT=1
NISPLUS_SERVER=0
NISPLUS_CLIENT=0
NIS_DOMAIN=stsd
MAX_NISCHECKS=2
EMULYP=""
YPSERV_OPTIONS=""
YPBIND_OPTIONS="-ypset"
YPPASSWDD_OPTIONS="/etc/passwd -m passwd PWFILE=/etc/passwd"
KEYSERV_OPTIONS=""
YPUPDATED_OPTIONS=""
YPXFRD_OPTIONS=""
RPC_NISD_OPTIONS="$EMULYP"
NIS_CACHEMGR_OPTIONS=""
YPSET_ADDR="koala.india.hp.com"
LONGNAMES_OPTIONS="group.bygid.dir group.bygid.pag group.byname.dir \
group.byname.pag hosts.byaddr.dir hosts.byaddr.pag \
hosts.byname.dir hosts.byname.pag networks.byaddr.dir \
networks.byaddr.pag networks.byname.dir networks.byname.pag \
passwd.byname.dir passwd.byname.pag passwd.byuid.dir \
passwd.byuid.pag protocols.byname.dir protocols.byname.pag \
protocols.bynumber.dir protocols.bynumber.pag \
rpc.bynumber.dir rpc.bynumber.pag services.byname.dir \
services.byname.pag ypservers.dir ypservers.pag"

SHORTNAMES_OPTIONS="group.bygi.dir group.bygi.pag group.byna.dir \
group.byna.pag hosts.byad.dir hosts.byad.pag \
hosts.byna.dir hosts.byna.pag netwk.byad.dir \
netwk.byad.pag netwk.byna.dir netwk.byna.pag \
passw.byna.dir passw.byna.pag passw.byui.dir \
passw.byui.pag proto.byna.dir proto.byna.pag \
proto.bynu.dir proto.bynu.pag rpc.bynu.dir \
rpc.bynu.pag servi.byna.dir servi.byna.pag \
ypservers.dir ypservers.pag"




Thanks,
Ravi kumar.R
Dennis Handly
Acclaimed Contributor

Re: NIS domain is not bound

client# ypwhich
NIS domain is not bound

Strange, I just had to fix this problem on my workstation. All of a sudden yesterday I got these errors. I just did the following and everything is ok:
# /sbin/init.d/nis.client stop
# /sbin/init.d/nis.client start
Ravi kumar raju
Advisor

Re: NIS domain is not bound

Every time i am using this command only. But after some time this bind issue is coming. I need to fix this issue permanently.
Peter Nikitka
Honored Contributor

Re: NIS domain is not bound

Hi,

I suspect, that this entry creates problems at boot time:
YPSET_ADDR="koala.india.hp.com"

As the variablename suggests, I would use an IP-address here.
- my need a running NIS to resolve that name
- dependence of name resolution (at boot time) to what is configures in /etc/nsswitch.conf
- even an entry in /etc/hosts may be used only after delays due to /etc/nsswitch.conf

mfG Peter
The Universe is a pretty big place, it's bigger than anything anyone has ever dreamed of before. So if it's just us, seems like an awful waste of space, right? Jodie Foster in "Contact"
Safarali
Valued Contributor

Re: NIS domain is not bound

Ravi Kumar

Your problem is name resultion issue as peter told, you can put ip address instead of fully qualified name

Regards
Safar
Ravi kumar raju
Advisor

Re: NIS domain is not bound

Yes, I did two corrections in my Nis client side

1) As per Peterâ s suggestion I gave ip address 2) I have created a nis slave server in that subnet.

Now I am observering both client for two week.
Ravi kumar raju
Advisor

Re: NIS domain is not bound

my problem has been solved.
Safarali
Valued Contributor

Re: NIS domain is not bound

Hi Ravi
if you are happy with our solutions please assign the points to the providers it will provide more motivation to help others

Regards
Safar