On 2017-10-25, Stefan Monnier <monn...@iro.umontreal.ca> wrote: >>> With such a setup, your host should correctly use your local `bind` >>> server, and if you ever stop your `bind` server it should start using >>> your ISP's server instead. And when you restart your `bind` server, it >>> will switch back to using that. >> That is not at all what I am trying to accomplish. I simply want >> resolv.conf to be left alone. As I do not have resolvconf even >> installed, I don't think I am asking too much. > > Don't worry, you can ask whatever you want and I won't judge if it's too > much or too little: It's not like I (nor anyone else for that matter) > have to provide you with what you want, anyway. > > 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. >
I thought the canonical method which was discussed in the long thread here recently was to use hooks: Create a file 'disable_make_resolv_conf' /etc/dhcp/dhclient-enter-hooks.d/disable_make_resolv_conf with the following #!/bin/sh make_resolv_conf(){ exit 0 } which does precisely nothing. Make it executable. -- "A simpering Bambi narcissist and a thieving, fanatical Albanian dwarf." Christopher Hitchens, commenting shortly after the nearly concurrent deaths of Lady Diana and Mother Theresa.