Comment 5 for bug 415676

#50430 is titled "NIS has problems starting before the network comes up" which is not the case here. The machine is up & running, network is working fine, but "apt-get install nis" is still showing this behaviour:

-------------------------------
Selecting previously deselected package nis.
Unpacking nis (from .../nis_3.17-12ubuntu1_i386.deb) ...
Setting up libslp1 (1.2.1-7.1) ...

Setting up nis (3.17-12ubuntu1) ...
 * Setting NIS domainname to: int.domain.org
 * Starting NIS services
 * binding to YP server...
 * ....
[...]
 * ....
   ...fail!
   ...done.
# netstat -anptu | grep yp
tcp 0 0 0.0.0.0:760 0.0.0.0:* LISTEN 5247/ypbind
udp 0 0 0.0.0.0:49725 0.0.0.0:* 5247/ypbind
udp 9240 0 0.0.0.0:759 0.0.0.0:* 5247/ypbind
-------------------------------

FWIW, debconf is configured to "low" priority, so it should've asked for missing values to start properly, e.g. let the installer choose between a client and/or server installation of NIS. It obviously cannot "bind to YP server" when no one has been configured yet.