:: Re: [DNG] hijacking resolv.conf - p…
トップ ページ
このメッセージを削除
このメッセージに返信
著者: sawbona
日付:  
To: Didier Kryn "Dng"
題目: Re: [DNG] hijacking resolv.conf - possible fix?
Hello:

On 22 Mar 2025 at 10:04, Didier Kryn wrote:

> ... better not make resolv.conf immutable.

Like I said in a previous post: [/etc/resolv.conf] is a system file
and not meant to be immutable.

It is a hack, not a solution to the problem of [/etc/resolv.conf]
being hijacked by an installed system package, its content overridden
without the systems owner knowing about it or being given a way out
of the mess created.

When I started this thread I was hoping to get to the root of the
problem and, with Ralph R.'s comment I did.

As you may have read, the root of this problem is the implementation
of a *feature* (in the DHCP, no matter how long ago) that, in my
opinion, should have never been implemented.

For whatever reason, it was given a green light by the powers that be
and did not produce much of anything till [connman] and other
connection managers silently made use of said feature and screwed
things up for eveyone who had the cheek of wanting to use their own
DNS settings.

I really could not give a rat's toss as to what DNS my ISP wants me
to use and I fail to see the advantage of the aforementioned
*feature* for me or for any other normal Linux user.

But if for whatever 'poetterinesque' reason it had to be implemented,
then an easy and straightforward way to disable it *should* have been
there for all users to rely on.

Like I proposed earlier: it should be an option at install time and a
script (just like reconfiguring your keyboard) made available to
disable it if you were not paying attention or came to your senses.

[code]
eg:
# dpkg-reconfigure dns-screwup
[/code]

A great many posts have proposed solutions that go from the simply
implemented to stuff that require poring over man pages and manuals,
a big thank you to all those who took the time to post them.

But that is *not* how this crap will get fixed.

We should not be having to devise workarounds (complex or not) to
dumb implementations such as this one, we should make our voice
heard.

I will now step off my box and go get me a much needed espresso.

Have a good week-end.

Best,

A.