[SOLVED] resolv.conf NOT sticking

PROBLEMCHYLD · 02-10-2019, 11:50 AM

I've added

Code:

nameserver 127.0.0.1
lookup file bind

to my resolv.conf file and it does NOT stay after reboot. How can I fix this? This is needed to run a private DNS over Tor.. Thanks

smallpond · 02-10-2019, 12:03 PM

Is Network Manager running?

PROBLEMCHYLD · 02-10-2019, 12:22 PM

Yes!!

pan64 · 02-10-2019, 12:33 PM

so resolv.conf is generated by networkmanager.
https://ma.ttias.be/centos-7-network...tcresolv-conf/
https://manpages.debian.org/jessie/n...conf.5.en.html see option dns

PROBLEMCHYLD · 02-10-2019, 12:54 PM

This link worked for me,

Quote:

Originally Posted by pan64

so resolv.conf is generated by networkmanager.
https://ma.ttias.be/centos-7-network...tcresolv-conf/

using

Code:

dns=none

Thanks....

Didier Spaier · 02-10-2019, 01:54 PM

Another way is to make /etc/resolv.conf immutable. As root:

Code:

chattr +i /etc/resolv.conf

PROBLEMCHYLD · 02-10-2019, 02:03 PM

Quote:

Originally Posted by Didier Spaier

Another way is to make /etc/resolv.conf immutable. As root:

Code:

chattr +i /etc/resolv.conf

I did read about that command but was hesitant because a lot of people opposed. How would you reverse the command?

pan64 · 02-10-2019, 02:05 PM

see man chattr

Code:

The format of a symbolic mode is +-=[aAcCdDeijsStTu].

The  operator  '+'  causes  the  selected attributes to be added to the
existing attributes of the files; '-' causes them to  be  removed;

But anyway I do not suggest you to do that way.

Didier Spaier · 02-10-2019, 04:01 PM

Quote:

Originally Posted by pan64

But anyway I do not suggest you to do that way.

Why not?

pan64 · 02-10-2019, 04:09 PM

just I don't know how will networkmanager handle the situation. I think it will fail in this case.

Didier Spaier · 02-10-2019, 04:27 PM

Quote:

Originally Posted by pan64

just I don't know how will networkmanager handle the situation. I think it will fail in this case.

No, it works. I sometime use that to avoid using the DNS servers of my web provider, not responsive at times.

PROBLEMCHYLD · 02-10-2019, 05:04 PM

Quote:

Originally Posted by Didier Spaier

No, it works. I sometime use that to avoid using the DNS servers of my web provider, not responsive at times.

I'll give your method a shot when I get my SSD and 16gb ram on a clean install Slackware64 in the near future. Thanks for multiple methods......

FlinchX · 02-14-2019, 02:04 AM

Just for the record: if you're not using Network Manager but you're pulling network settings info via DHCP, your resolv.conf file may get overwritten as well. To prevent that, see /etc/rc.d/rc.inet1.conf and search for 'DHCP_KEEPRESOLV' setting there.

PROBLEMCHYLD · 03-26-2019, 11:55 PM

Quote:

Originally Posted by Didier Spaier

Another way is to make /etc/resolv.conf immutable. As root:

Code:

chattr +i /etc/resolv.conf

This method is very aggressive and I love it. Thanks!!!!!!