On 12/18/22 22:37, ToddAndMargo via users wrote:
On 12/18/22 18:00, Samuel Sieb wrote:
On 12/18/22 17:57, ToddAndMargo via users wrote:
On 12/18/22 17:10, Samuel Sieb wrote:
On 12/18/22 15:34, ToddAndMargo via users wrote:
Chuckle. All is took was giving the developers a
"doggy chew toy" (fake resolv.conf) to distract
them from messing up my networking and all suddenly
worked.
Clearly you missed the documentation that that's how to do it.
The must think everyone only has one network card.
Fedora Server folks must be crying blood.
No, it's specifically designed for multiple interfaces.
e.g. at work I have split-DNS so requests for a particular domain go
over the VPN that provides the connection to that network.
They did a really, really bad job of it.
Well, you're welcome to your opinion. But it's clearly working for
most people.
I am also welcome to my experience too.
Do those other people have FIVE network
interfaces (two physical) and an option
for another sixth virtual interface?
Do you really want to do this? :-)
I don't know about "those" people, but one server of mine has 12
interfaces including physical, vlans, vpns, and VMs and I have no
problems with it using only NetworkManager. I did override the
resolv.conf on that one with no problems because of some issue with
resolving at boot, probably related to the DNS server being in a VM that
wasn't up yet. Another server has 10 interfaces, but it still has the
default systemd-resolved config and is working fine and it has a similar
freeipa VM for DNS.
_______________________________________________
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
