On 12/19/22 13:01, Jonathan Billings wrote:
You saw how it fell apart when it put different
DNS servers on different interfaces and that
did not match resolv.conf? And how I kept
over riding my manual configurations.
This hurt me more than a Windows upgrade.
I use Linux to avoid that kind of nonsense.
I'm not sure how that's a good example.
If you are using systemd-resolved, then /etc/resolv.conf should simply have "nameserver 127.0.0.53"
It puts it there and things ago foo bar
for the nameserver. This is where the OS looks for name lookups when doing DNS lookups. Then systemd-resolved will have whatever different DNS servers, defined per interface along with which search paths that should be searched, as well as priority. That way you can have all your internal names go to one interface that's on the internal network, a certain name go to the virtual machine interface so it can manage DNS for local VMs (which libvirtd supports), your work domain goes to your VPN interface, and the rest go to your external interface for default resolution. If you're running bind, then you would just need to set the the IP for your installation as the default name server. For all of this, /etc/resolv.conf should remain using "nameserver 127.0.0.53".
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
