On Wed, 09 Apr 2025 05:17 -0300
Alexandros Prekates via Dng <dng@???> wrote:

> ... setting dns to a value that i want is a setting that should ...
Be the *exclusively* the sysadmin's choice and as such, one to be
respected by the system.

*Not* something that someone else (in my specific case, the network
manager application) decides for me on the basis of heaven knows what
bright idea they had that morning before being fully awake.

What makes it even worse is that (connman and network-manager) hijack
the system's DNS settings in a covert manner, without any prior
notice.

That was how all the systemd crap started.
And here we are.

Is it a political issue?
I could not give a monkey's toss whether it is political or not.
It is a rights/ownership issue:

*My* system?
*My* DNS settings.

The more I think of it the more it bothers me that this has gone on
for over a decade now and it *still* a problem.

And a *work-around* is not a suitable solution, this is something
that should have been nipped in the bud ages ago.

> ... during fresh devuan installations frequenlty i wonder ...
With all due respect, it is not something to wonder about.
It is a problem that must get fixed.

> ... setting dns to a value that i want is a setting that should be
> made early ...
Yes, it should definitely be a sysadmin's choice.

Early on I wrote:

> ... for the Linux installer process to ask if the default setting
> was acceptable to the user of the system being installed and also
> indicate how to change it if needed.
> eg: like when you need to reconfigure your keyboard.

Choosing how to manage my systems DNS and the way it will be done is
akin to choosing your keyboard layout, anguage settings or *anything
else* related to how my system works.

And a network manager application (ie: the developer who wrote it)
has absolutely no say in that.

None whatsoever.

> ... have a feeling that the dns choice crosslines with politics.
That is a deep rabbit hole to go into.

Ralph Ronnquist set me straight early on in this thread and wrote
that the Dynamic Host Configuration Protocol (DHCP) has for a long
time now given developers the data needed for screwing around with a
sysadmin's choice of DNS.

That being that the case, the system *itself* should have a clear and
easy way of preventing that from happening.

Next you know, someone will have yet *another* brain fart and decide
to hardcode DNS settings within the kernel.

Best,

A.