NIS client (ypbind) fails during system bootup with "NIS server for domain <domainname> is not responding."

Solution Verified - Updated -

Issue

  • ypbind.service failed to start at system boot, but systemctl start ypbind.service by root is successful.

Environment

  • Red Hat Enterprise Linux 8
  • NIS Client
  • ypbind

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content