Peter. Considering your 5 years here and the topic of systemd-resolved. I was
wondering if you could help me to propose a default change to the installation
of systemd-resolved that seems to have helped me keep it installed and working
even with a Local DNS server in the mix.
This approach https
On 6/5/22 17:18, stan via users wrote:
On Sat, 4 Jun 2022 16:07:12 -0400
Tom Horsley wrote:
Try editing /etc/NetworkManager/NetworkManager.conf and putting
dns=none after the [main] section entry.
I have to do this in order to use dns servers other than those the ISP
provides with knot-reso
> On 4 Jun 2022, at 21:07, Tom Horsley wrote:
>
> On Sat, 04 Jun 2022 15:55:53 -0400
> Sam Varshavchik wrote:
>
>> this ends up creating /etc/resolv.conf as a plain file, rather than a
>> symlink. But, I suppose, that works too.
>
> Perhaps people who want their own damn resolv.conf file
>
On Sat, 4 Jun 2022 16:07:12 -0400
Tom Horsley wrote:
> Try editing /etc/NetworkManager/NetworkManager.conf and putting
> dns=none after the [main] section entry.
I have to do this in order to use dns servers other than those the ISP
provides with knot-resolver.
_
On Sat, 04 Jun 2022 15:55:53 -0400
Sam Varshavchik wrote:
> this ends up creating /etc/resolv.conf as a plain file, rather than a
> symlink. But, I suppose, that works too.
Perhaps people who want their own damn resolv.conf file
are missing this obscure setting:
Try editing /etc/NetworkManager
Petr Menšík writes:
Symlinks obviously ends with non-expected SELinux contexts. I think this is
actually a bug in SELinux policy for Network Manager. Because target file
has wrong selinux context.
$ ls -Z /run/NetworkManager/no-stub-resolv.conf
system_u:object_r:NetworkManager_var_run_t:s0
Symlinks obviously ends with non-expected SELinux contexts. I think this
is actually a bug in SELinux policy for Network Manager. Because target
file has wrong selinux context.
$ ls -Z /run/NetworkManager/no-stub-resolv.conf
system_u:object_r:NetworkManager_var_run_t:s0
/run/NetworkManager/no-
On Sat, 28 May 2022 08:51:08 -0400
Sam Varshavchik wrote:
> It seems that uninstalling systemd-resolved and repointing /etc/resolv.conf
> ends up breaking chrony:
The simplest fix is the also remove chrony and install ntp.
___
users mailing list -- us
It seems that uninstalling systemd-resolved and repointing /etc/resolv.conf
ends up breaking chrony:
type=AVC msg=audit(1653741361.179:318): avc: denied { getattr } for
pid=856 comm="chronyd" path="/run/NetworkManager/no-stub-resolv.conf"
dev="tmpfs" ino=1525 scontext=system_u:system_r:c
