Alexandros Prekates via Dng <dng@???> wrote:

>> The web is full of posts complaining about this issue from quite a
>> few years back, all of which have been ignored.
>>
>
> I was complaining also a couple of days ago in irc/libera/#devuan and in
> irc/oftc/#qemu !
>
> Devuan on qemu with user network backend has /etc/resolv.conf set to
> 10.0.2.3 (DNS) . That doesnt work. When i changed it to 8.8.8.8 or
> 10.0.2.2 (host) both worked. But at reboot /etc/resolv.conf again
> it was set to 10.0.2.3.

Let me translate: My network is not properly configured and it’s the developers fault fore shipping something that works for most users in a correctly configured network, while I bear zero responsibility for fixing my broken network settings.

> Well in #devuan i was also told to make file immutable.

Because too many people can’t cope with the idea of fixing the underlying problem ?


> Being a sysadm on a system that dont respect your choices but someone
> else choices is a rather peculiar predicament for a devuan sysadm to
> fall into having in mind how devuan started over a choice policy.

As previously explained, this IS under your own control. There are settings to do just that.

And also as explained, systems do have to have default settings*, and the default settings do work for the majority of users.


* Unless you argue that there should be no defaults, and every user should have to configure (probably) hundreds of settings correctly if they want a working system.




> Alexandros Prekates via Dng <dng@???> wrote:
>
> On Wed, 9 Apr 2025 04:56:43 -0400
> Dan Purgert via Dng <dng@???> wrote:
>
>
>>>
>>> Devuan on qemu with user network backend has /etc/resolv.conf set
>>> to 10.0.2.3 (DNS) . That doesnt work. When i changed it to 8.8.8.8
>>> or 10.0.2.2 (host) both worked. But at reboot /etc/resolv.conf again
>>> it was set to 10.0.2.3.
>>
>> Fix your DHCP server, so it's not handing out incorrect DNS Server
>> info
>>
>
> Thanks your advice. Is there a guide on how to troubleshoot dns and
> fix possibly incorrect dns server info ?

You’ve already diagnosed the problem.

For you, the correct setting for DNS server is 10.0.2.2 (or 8.8.8.8), your DHCP server is handing out 10.0.2.3. Go to your DHCP server and change the setting where it’s configured to hand out 10.0.2.3 so it hands out 10.0.2.2 (or 8.8.8.8).

OR

If 10.0.2.3 is actually correct for most of the network and it’s just this host that’s needs 10.0.2.2, then configure the DHCP client and/or network manager on the host to not mangle resolve.conf.



In the grand scheme of things, in a world where systemd is trying to take over and really disrespect your wishes, this is a fairly minor nit.


My 2d worth, Simon