Subject: | yp_bind only works with the default domain |
Date: | Thu, 1 Aug 2019 22:24:55 +0000 |
To: | "bug-Net-NIS [...] rt.cpan.org" <bug-Net-NIS [...] rt.cpan.org> |
From: | "Seip, Christopher" <chris.seip [...] hpe.com> |
I can't see how to get Net::NIS::yp_bind(domainname) to work with a domain other than the one bound to in the local host's OS. If I reference this "non-native"/non-default NIS domain in a yp_bind() call or tieing to a Net::NIS object, I get the message "YPBINDPROC_DOMAIN: Domain not bound".
To configure for the possibility of this working, I have the local host's NIS servers mentioned in /etc/yp.conf as well as the "non-native" NIS servers, e.g.:
domain mydomain server mymaster.mydnsdomain
domain mydomain server myslave.mydnsdomain
domain otherdomain server othermaster.mydnsdomain
domain otherdomain server otherslave.mydnsdomain
Is a Net::NIS client capable of binding to a separate domain from its host OS? Or does it just talk with the local ypbind process? There's some "bind this process" language in the Net::NIS perldoc page that suggests it might be capable of binding to a separate domain, as far-fetched as that seems. So I've pursued this possibility a bit.
Is this a bug, a mis-configuration, or just something that Net::NIS will never be able to do? Thanks in advance for any feedback (if anyone steps in to maintain it or comment).
Perl: 5.26.1
Module: Net::NIS version 0.44
Distro: Ubuntu 18.04.2 LTS (Bionic Beaver)