fedora-server

#106 Add steps to dnsmasq setup guide to avoid conflicts with systemd-resolved
Merged by aggraxis. Opened by tsobczynski.
tsobczynski/fedora-server dnsmasq-admin-docs  into  main

Download 106.patch

I added steps to disable the systemd-resolved stub resolver and trigger Network Manager to produce a suitable /etc/resolv.conf to make use of dnsmasq. Without these additional steps, I found that name resolution was broken at the end of dnsmasq setup on Fedora Server 37. Note that there is a related issue with a patch in Network Manager to fix a problem generating the search domain in resolv.conf: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1281

Thanks for the contribution and sorry for the long delay. Unfortunately, I couldn't manage to make it in time. I'll check your proposal with 39 now.

Understood. Thank you for the update! =E2=80=94Tom

On Wed, Jan 10, 2024 at 6:29=E2=80=AFAM Peter Boy pagure@pagure.io wrote:

pboy commented on the pull-request: Add steps to dnsmasq setup guide to avoid conflicts with systemd-resolved that you are following:
Thanks for the contribution and sorry for the long delay. Unfortunately, = I couldn't manage to make it in time. I'll check your proposal with 39 now.

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-server/pull-request/106

rebased onto cdc548ca43a85f402bd6537ce378ae209090b2d5

I realize this is so very late, but this documentation looks good to me. I have to do the same thing in order to get pihole to work properly on Fedora Server. (Which is doing dnsmasq as well.)

Pull-Request has been merged by aggraxis

I'm happy that this tiny contribution was ultimately merged. Thanks much for taking the time to get this into the docs!
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.