Skip to content

Instantly share code, notes, and snippets.

@dragonfire1119
Last active March 23, 2025 08:14
Show Gist options
  • Save dragonfire1119/bd3a1883ec1e36d9d15500eb75796014 to your computer and use it in GitHub Desktop.
Save dragonfire1119/bd3a1883ec1e36d9d15500eb75796014 to your computer and use it in GitHub Desktop.
Disable systemd-resolved

Check and see if port 53 is taken:

lsof -i :53

OR

netstat -tulpn | grep ":53 "

Disable and stop the systemd-resolved service:

sudo systemctl disable systemd-resolved.service
sudo systemctl stop systemd-resolved.service
@huesofredy
Copy link

I can't deactivate the port, it gives me this error when launching the last command

ash-4.4# sudo systemctl stop systemd-resolved.service
Failed to stop systemd-resolved.service: Unit systemd-resolved.service not loaded. ¿?

@ilariima
Copy link

same problem getting this error:
#Failed to disable unit: Unit file systemd-resolved.service does not exist.
#Failed to stop systemd-resolved.service: Unit systemd-resolved.service not loaded.

@supermario5757
Copy link

same

@TheNilesh
Copy link

On casaos/rpi, the port 53 is occupied by docker-proxy process and not systems. Hence the commands wont work, I'm afraid to kill docker-proxy, what if it takes down casaos? Any expert please help

$ sudo netstat -tulpn | grep ":53 "
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      1152/docker-proxy   
tcp6       0      0 :::53                   :::*                    LISTEN      1166/docker-proxy   
udp        0      0 0.0.0.0:53              0.0.0.0:*                           1182/docker-proxy   
udp6       0      0 :::53                   :::*                                1198/docker-proxy 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment