> So, outside of classic Unix/Linux /etc/resolv.conf... most software does
> not treat a list of multiple DNS servers as explicitly "primary" and
> "secondary" (and so on).
Both network manager and systemd-resolved ostensibly support ordering of DNS
servers. I'm not sure why you have decided to
Once upon a time, Tom Seewald said:
> Yeah I'm not very happy that systemd-resolved seemingly does this silently
> and that I have to just restart the service for it to try again. My server is
> just a consumer router running OpenWRT which uses Dnsmasq.
So, outside of classic Unix/Linux /etc/re
I could just disable it, but given that systemd-resolved is now a default of
Fedora I thought I'd bring this up as this is having a negative impact on my
experience with Fedora 33.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe s
On Mon, 26 Oct 2020 20:30:31 -
Tom Seewald wrote:
> Yeah I'm not very happy that systemd-resolved seemingly does this silently
> and that I have to just restart the service for it to try again.
You could just disable that service, then systemd wouldn't try to
cache dns. There are about a doz
Yeah I'm not very happy that systemd-resolved seemingly does this silently and
that I have to just restart the service for it to try again. My server is just
a consumer router running OpenWRT which uses Dnsmasq.
___
users mailing list -- users@lists.fed
On 26/10/2020 18:09, Patrick O'Callaghan wrote:
At the risk of beating a dead horse, I'll be "that guy" again and point
out that F33 is as yet unreleased and any issues should be sent to the
Fedora Test list until it is released.
Well, since F33 is a GO for release on Tuesday the 27th, I think
On Mon, 2020-10-26 at 02:30 +, Tom Seewald wrote:
> After upgrading to F33 I've noticed that sometimes my current DNS server
> switches to 1.1.1.1 instead of my local DNS (192.168.1.1). This has happened
> both immediately after system boot, and once after several hours of use. For
> my conn
On 26/10/2020 10:30, Tom Seewald wrote:
After upgrading to F33 I've noticed that sometimes my current DNS server switches to 1.1.1.1 instead of my
local DNS (192.168.1.1). This has happened both immediately after system boot, and once after several hours
of use. For my connection in Network Man
After upgrading to F33 I've noticed that sometimes my current DNS server
switches to 1.1.1.1 instead of my local DNS (192.168.1.1). This has happened
both immediately after system boot, and once after several hours of use. For my
connection in Network Manager, under IPv4, I have "192.168.1.1, 1.
