On Thursday 27 October 2016 21:03:21 Glenn English wrote: > Does anyone know how to get rid of resolvconf? > > I'm putting a server together, and resovlconf keeps wiping my > /etc/resolv.conf file and replacing the nameserver IP with "# Created > by resolvconf" (approx). No nameserver, no anything. > > I removed it with Aptitude, and the file started talking about being > built with dhcpd. Nameserver still wiped, and Aptitude says there's no > package called dhcpd. > > These things seem to be triggered by an ifupdown, to either state. I > removed some cruft that triggered it; now ifupdown doesn't any more, > but a reboot does. As best I can tell, there's nothing in man or on > the 'Net about removing it or just making it stop killing my > nameserver file. > > This is a server. It will have a very stable nameserver IP. I'd like > to be able to create a file containing the IP and not have 'helpful' > software scribble on the file. > > Any and all suggestions will be appreciated...
At high risk of starting another flame war about network-manager, nuke that puppy with extreme prejudice. Set up an /etc/hosts file with the address FQDN alias of every other machine including itself, on your local network. Mine has about 10 entry's ATM. Then fix resolv.conf to be a REAL file, it may be a link. Contents: nameserver add.ress.of.router #that couples your machines to the network using NAT order host,dns domain yourlocaldomain.name Then: sudo chmod +i /etc/resolv.conf So nothing can scribble over it. Then in the /etc/networking/interfaces file, add: auto eth0 # regular network for local domainname iface eth0 inet static # machines local address, matches hosts file entry address 192.168.XX.ZZ netmask 255.255.255.0 # the XX's can be anything up to 253, but I'd avoid 0,1,2 as its too common, they must all match. # routers address below so it will fwd all dns queries to you ISP if setup correctly. gateway 192.168.XX.1 And write it, then do the chmod +i on it too to prevent its getting scribbled on.. sudo service network restart, and your network should just work. From then on. Now this of course isn't going to work if you are carrying a lappy and expecting to tap the wifi at any Starbucks you pull into. Then you are truly at the mercy of network-mangler, which might work but usually doesn't. My experience with earlier versions of it was very intermittent at best. Now, save your flames, I already put on my nomex suit. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
