On Mon, 2020-10-26 at 02:30 +0000, 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 Manager, under IPv4, I have "192.168.1.1, 1.1.1.1" in "Other DNS Servers". My understanding is that this should cause the system to prefer 192.168.1.1, and historically it has always consistently used 192.168.1.1 until the upgrade to F33. At first glace I don't see any relevant messages in the system journal that indicate why it is falling back to 1.1.1.1. The output of "resolvectl status" shows that 192.168.1.1 is listed above 1.1.1.1 both when it is correctly using local dns and when it is spuriously switching to 1.1.1.1. > > My current workaround is to restart the resolved service, which causes it to switch back to the correct DNS server, however this is clearly not ideal. > > Any ideas for fixing or troubleshooting this would be appreciated. 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. To repeat: many testers do not read the Users list and will not see your post. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
