Skip to content

RS: Prevent dnsmasq from using port 53 #1610

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 29 additions & 1 deletion content/embeds/port-53.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
If port 53 is in use, the installation fails. This issue can occur in default installations of certain operating systems in which `systemd-resolved` (DNS server) is running.
If port 53 is in use, the installation fails. This issue can occur in default installations of certain operating systems in which `systemd-resolved` (DNS server) or `dnsmasq` is running.

To prevent this issue, change the system configuration to make this port available before installation.

To prevent `systemd-resolved` from using port 53:

1. Edit `/etc/systemd/resolved.conf`:

```sh
Expand Down Expand Up @@ -31,3 +33,29 @@ You might encounter a temporary name resolution error (`sudo: unable to resolve
```sh
sudo service systemd-resolved restart
```

To prevent `dnsmasq` from using port 53:

1. Stop the `dnsmasq` service if it's running:

```sh
sudo systemctl stop dnsmasq
```

1. Prevent `dnsmasq` from starting automatically at system boot:

```sh
sudo systemctl disable dnsmasq
```

1. Mask `dnsmasq` to prevent it from being started manually or by other services:

```sh
sudo systemctl mask dnsmasq
```

1. Verify `dnsmasq` is no longer active and won't start at system boot:

```sh
sudo systemctl status dnsmasq
```