Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 11316 - ypbind doesn't...
ypbind doesn't...
Status: CLOSED DUPLICATE of bug 11235
Product: Red Hat Linux
Classification: Retired
Component: ypbind (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
Depends On:
  Show dependency treegraph
Reported: 2000-05-08 19:49 EDT by martin
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-05-22 11:54:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description martin 2000-05-08 19:49:53 EDT
If there is no name server available at boot time (i.e. because the
ypclient in question is the name server, and BIND starts after ypbind)
ypbind will fail to bind if the server is specified in /etc/yp.conf a la:

  domain ypdomain server ypserver.mydomain.com

Or, to be more specific, ypbind WILL NOT use /etc/hosts to determine the
hostname of the server specified in /etc/yp.conf and therefore if there is
no dns server available, the ypbind will fail.

One workaround is to change the start order of named to preceed ypbind.
IIRC, I was able to use the server's IP address in place of its name, and
that did work, but I don't remember for certain now.

This is ypbind-3.3-24, which ships with RH6.1 -- I did not see any updates
for this package in the updates directory.
Comment 1 Cristian Gafton 2000-05-22 11:54:59 EDT
assigned to laroche
Comment 2 Preston Brown 2000-10-16 15:20:39 EDT

*** This bug has been marked as a duplicate of 11235 ***

Note You need to log in before you can comment on or make changes to this bug.