There is another thread re systemd-resolved and adguard.
Ed Greshko had a solution to use /etc/resolve.conf instead of the stub file
systemd-resolved uses.
"To revert to the previous behavior you need to remove the symbolic link
lrwxrwxrwx. 1 root root 39 Sep 1 17:52 resolv.conf ->
../run/syst
On Sun, 15 Nov 2020 at 20:22, Tom H wrote:
> On Sun, Nov 15, 2020 at 10:15 AM Anthony F McInerney
> wrote:
>
>
> > Can someone explain why systemd-resolved needs to symlink
> > /etc/resolv.conf to 4(or more) different places, instead of just
> > having those 'detected things' as options in
> > /
On Sun, Nov 15, 2020 at 10:15 AM Anthony F McInerney
wrote:
> Can someone explain why systemd-resolved needs to symlink
> /etc/resolv.conf to 4(or more) different places, instead of just
> having those 'detected things' as options in
> /etc/systemd/resolved.conf ?
The different symlinks/files p
On Sat, 14 Nov 2020 at 19:35, Sam Varshavchik wrote:
> Anthony F McInerney writes:
>
> >Note that the selected mode of operation for this file is
> detected
> > fully automatically, depending on whether /etc/resolv.conf is a symlink
> to
> >/run/systemd/resolve/resolv.conf or list
Anthony F McInerney writes:
Note that the selected mode of operation for this file is detected
fully automatically, depending on whether /etc/resolv.conf is a symlink to
/run/systemd/resolve/resolv.conf or lists 127.0.0.53 as DNS server.
Again: why does anything have to be "det
> It is a malignant carcinoma.
Okay, seriously y'all. This over-the-top animosity is not welcome here. This
is a Fedora list, and we expect discourse to remain civil. If you don't like
it, fine.
You have a number of options, including working on a Fedora spin which
configures things differently.
No.
It is a malignant carcinoma.
From: "Tom Horsley" mailto:horsley1...@gmail.com>>
Date: Saturday, 14 November 2020 at 15:16:35
To: "users@lists.fedoraproject.org"
mailto:users@lists.fedoraproject.org>>
Subject: Re: systemd-resolved breakage
On Sat, 14 Nov
On Fri, 13 Nov 2020 at 23:42, Sam Varshavchik wrote:
> Petr Menšík writes:
>
> > Am I missing something?
>
> Yes, system is being shoved down your gullet, whether you like it or not.
>
> > would NetworkManager.conf:
> > dns=default
> >
> > Write resolv.conf again? Can I make it rewrite after disa
On Sat, 14 Nov 2020 11:56:01 +0100
Tom H wrote:
> > Yes, system is being shoved down your gullet, whether you like it
> > or not.
>
> Whichever distribution you use, you're at the mercy of its developers.
> In this particular case, the developer responsible for the change
> didn't care about br
On Sat, Nov 14, 2020 at 12:42 AM Sam Varshavchik
wrote:
> Petr Menšík writes:
>>
>> Am I missing something?
>
> Yes, system is being shoved down your gullet, whether you like it
> or not.
Whichever distribution you use, you're at the mercy of its developers.
In this particular case, the developer
Petr Menšík writes:
Am I missing something?
Yes, system is being shoved down your gullet, whether you like it or not.
would NetworkManager.conf:
dns=default
Write resolv.conf again? Can I make it rewrite after disabling
systemd-resolved? Why doesn't it restore /etc/resolv.conf on
systemd-re
On Fri, Nov 13, 2020 at 3:17 PM Petr Menšík
wrote:
>
> Sad thing is, I want Network Manager to write my resolv.conf as it
> did before. I just want systemd-resolved disabled and keep simple
> text file in /etc/resolv.conf.
>
> I haven't found automatic way to recover my system, after I do:
> syste
On Fri, Nov 13, 2020 at 2:22 PM Tom Horsley wrote:
> systemctl stop systemd-resolvd
> systemctl disable systemd-resolvd
resolved
> Edit /etc/NetworkManager/NetworkManager.conf And in the [main]
> section stick this:
>
> [main]
> dns=none
Since "/etc/NetworkManager/NetworkManager.conf" is
"%c
Sad thing is, I want Network Manager to write my resolv.conf as it did
before. I just want systemd-resolved disabled and keep simple text file
in /etc/resolv.conf.
I haven't found automatic way to recover my system, after I do:
systemctl disable --now systemd-resolved
It keep broken /etc/resolv.c
(Relatively) simple fix:
systemctl stop systemd-resolvd
systemctl disable systemd-resolvd
Edit /etc/NetworkManager/NetworkManager.conf And in the [main]
section stick this:
[main]
dns=none
Now rm -f /etc/resolv.conf
Now create your own /etc/resolv.conf file from scratch with
the nameserver and
I was surprised that a
dig www.unicode.org a
was coming back with a SERVFAIL. I have bind running on the same server, so
I thought it just had a hiccup. Just to be sure I haven't fat-fingered
anything and accidentally set dns lookups to go to another dns server on the
network, I did an exp
16 matches
Mail list logo
