I've tested nis nis_3.17.1-1 and nis_3.17.1-2 on a nis client running buster. nis_3.17.1-1 works without problems. After a reboot, nis is running.
With nis_3.17.1-2, after a reboot nis is not working. If I log in via the console and do a systemctl restart nis, ypbind is not started. But when I just call ypbind, it gets started and nis is working. So the problem is not in the nis package itself. ypbind is not started if systemd is trying to start it. How can we debug this in more detail? -- regards Thomas