Re: systemd-resolved switching DNS servers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 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.



This would seem to indicate that at some time 192.168.1.1 failed to respond to a DNS request.

I replicated this by using a firewall on a DNS server to block request.

Prior to the block I see

  Current DNS Server: 192.168.1.142
         DNS Servers: 192.168.1.142
                      192.168.1.1

After the block I see

  Current DNS Server: 192.168.1.1
         DNS Servers: 192.168.1.142
                      192.168.1.1

I don't see any reports in the journal that a DNS request failed to 192.168.1.142.

After removing the firewall block the Current DNS remains at 192.168.1.1.  I could not
find any configuration or settings that would have systemd-resolved reassess access to
the "primary" DNS server.

What type of server is your server at 192.168.1.1?

---
The key to getting good answers is to ask good questions.

_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux