Topicality of NIS when configuring new devices? NIS is insecure, and anything new being stood up in production should almost certainly not be consuming it. With this in mind I started a close vote on this question, but on further thought this seemed worth discussing on meta. While NIS is something that a system administrator can expect to run into within legacy environments and may have questions in regards to, should we be be providing support for it when it's clear that someone is standing up _new_ devices that are consuming it?

If someone was trying to set up a _completely new installation of NIS_ , that would certainly be misguided. Pointing new devices at an existing NIS infrastructure is another matter though: most of the people in this situation don't really have a choice in the matter, usually for reasons of budget or management restriction.

Even though it's less than ideal to point new devices at old infrastructure such as this (it adds to the technical debt of the larger problem), the questions are reasonable ones and there is no reason to turn them aside.

(In hindsight, I apologize for my misguided question.)