resolv.conf rewrites to 127.0.0.1

[kobak]

My resolv.conf always rewrites the nameserver to 127.0.0.1. I had pi-hole installed for a while, but didn't need it anymore. It should be simple, but can't find what is rewriting my nameserver to 127.0.0.1.

Thanks.

[epoch1970]

Usually resolv.conf points to the localhost when a DNS service is installed. Do you have dnsmasq installed?
It works as a local cache (and resolver) so it might be a good thing to keep it and tweak /etc/dnsmasq.conf. Unless your DNS service is handled elsewhere already.

This being said, does /etc/resolv.conf start with this?

Code: Select all

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

If the answer is yes, have a look at resolvconf.conf (...) and then look in the /etc/resolvconf directories. There could be a script called dnsmasq somewhere in there, move it out of the way, reboot and see how it fares.

[DougieLawson]

Are you running dsnmasq? It will re-write your /etc/resolv.conf

One way to protect it is sudo chattr +i /etc/resolv.conf after you've edited it to have sensible contents. That prevents anyone updating it unless they run sudo chattr -i /etc/resolv.conf first.

[epoch1970]

Making /etc/resolv.conf immutable has to be one of the worst hacks around.
Don't do that. When the resolver is hosed your machine is hosed.

[DougieLawson]

Making /etc/resolv.conf immutable has to be one of the worst hacks around.
Don't do that. When the resolver is hosed your machine is hosed.

I disagree.

I do it on all of my fixed RPis that are permanently booted and connected. It saves a bunch of hassle when things like dhcp and dnsmasq want to tamper with my settings. I've got complete control including adding the IPv6 & IPv4 addressed of my bind9 system to /etc/resolv.conf in the other fourteen raspberries.

If I'm taking a Raspberry out of my network I'll undo it. Not being able to resolve a domain to an IP is no big deal and is a trivial problem to diagnose and cure.

[epoch1970]

dnsmasq is not an insignificant program, people could learn how to use it.
Abusing a system lib is bad practice, no need to promote that.

(Named here, too.)

[n67]

dnsmasq is not an insignificant program, people could learn how to use it.
Abusing a system lib is bad practice, no need to promote that.

(Named here, too.)

Let not this generally correct principle blind you (or anyone else) to the cold, hard fact that stuff has bugs in it. There are situations where you have to do stuff like this (e.g., use "chattr" to freeze a file) because it is just not practical to fix the underlying system software bugs.

Being able to whip up fixes like this on the fly is an important skill.

[epoch1970]

Except in this instance, there is no bug.
If there is one, please post to the dev lists of resolvconf or dnsmasq.

Last time. Making /etc/resolv.conf immutable is sloppy.
It will get you into trouble once you've forgotten you had the bright idea to pass that command, or whoever else uses the machine.
man resolvconf, man dnsmasq is all you need.

[n67]

First principle of computer programming: All code has bugs in it.