Add steps to dnsmasq setup guide to avoid conflicts with systemd-resolved #106
No reviewers
Labels
No labels
in progress
in progress
meeting
need info
ongoing work project
on hold
pending activity
release test
user documentation
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
server/user-documentation!106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dnsmasq-admin-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
rebased onto
cdc548ca43I 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!