docs: fix instructions for disabling systemd-resolved port 53 for fedora (still compatible with Ubuntu) - #1860
docs: fix instructions for disabling systemd-resolved port 53 for fedora (still compatible with Ubuntu)#1860LizenzFass78851 wants to merge 1 commit into
Conversation
Troubleshooting for Fedora. It is Ubuntu compatible. Signed-off-by: LizenzFass78851 <82592556+LizenzFass78851@users.noreply.github.com>
yubiuser
left a comment
There was a problem hiding this comment.
I still think all this configurations is better placed in https://docs.pi-hole.net/docker/
|
|
||
| For fedora users, you can run the following commands to edit the sysconfig(s) found at `/etc/NetworkManager/system-connections` via nmcli. | ||
|
|
||
| Example sysconfig nmcli commands: |
There was a problem hiding this comment.
I'm not sure if we should have instructions how to set Pi-hole as the DNS for the host at all. While this is a valid configurations, the host's DNS will break if Pi-hole is not running.
There was a problem hiding this comment.
For Ubuntu's netplan, there is already a similar example of how to use Pihole as a system DNS server in the operating system:
Lines 195 to 209 in ee0d04f
Therefore, the additionall instructions for set Pihole as a DNS server for the operating system for Fedora users.
There was a problem hiding this comment.
I see where you'e coming from. This is a more general discussion. (I think I meant to suggest to also move the Ubuntu part to the docs). Maybe @pi-hole/docker-maintainers have an opinion
|
Doc PR moving this to the other repo: pi-hole/docs#1266 I thin we can remove the whole section then and only leave a link. |
The pr #1863 to remove the section has been created |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
#1863 has been merged. |
Description
This supplements the instructions for deactivating systemctl resolve port 53 under Fedora, since one of the previous commands only works under Ubuntu (Debian).
Motivation and Context
How Has This Been Tested?
I created 4 VMs:
I tried the instructions for disabling systemd-resolve in all 4 VMs and found that, following the previous instructions, this no longer worked on Fedora 42. However, it did work on the other 3 VMs (as also noted in the linked issue).
After updating the documentation (readme.md), I tried the additions on Fedora 42 (and Fedora 33), port 53 was successfully disabled.
Types of changes
Checklist: