On Wed, Oct 25, 2017 at 12:42:24AM -0400, Stefan Monnier wrote: > > I just gave you a solution to your underlying problem, which *uses* the > infrastructure rather than fighting it. I won't force you to use it, tho. > Actually, that is not what you did. You provided a way to mask the problem. If you look at the subject line of my original message it is "Why does resolv.conf keep changing?" The problem I am trying to solve is to identify what on my system keeps changing resolv.conf despite the fact that I do not have the resolvconf package installed and that I have attempted every documented option to configure resolv.conf to my requirements that I could find associated with the network-related packages I have installed on my system.
I am not willing to accept that there is no way to identify what is going on that is causing resolv.conf to change. Once I have figured out what is chaning resolv.conf and why, then I will be willing to consider how best to accomplish my objective of keeping resolv.conf configured the way that suits my needs. That said, you keep touting that your suggestion sets the nameserver back to the ISP nameserver when bind is stopped. That may be an advantage to you, but it is specifically a behavior that I do not on my system. Regards, -Roberto -- Roberto C. Sánchez
