# port 53 is already in use

# [Update: What to do if port 53 is already in use](https://discourse.pi-hole.net/t/update-what-to-do-if-port-53-is-already-in-use/52033)

<div class="ember-view" id="bkmrk-"><div class="container"><div class="title-wrapper"></div></div></div><div class="container posts" id="bkmrk-when-the-port-53-is-"><div class="row"><section class="topic-area" data-topic-id="52033" id="bkmrk-when-the-port-53-is--0"><div class="posts-wrapper"><div class="ember-view" id="bkmrk-when-the-port-53-is--1"><div class="post-stream"><div class="topic-post clearfix topic-owner regular"><article aria-label="post #1 by @Zopyrus" class="boxed onscreen-post" data-post-id="191464" data-topic-id="52033" data-user-id="26994" id="bkmrk-when-the-port-53-is--2" role="region"><div class="row"><div class="row"><div class="topic-body clearfix"><div aria-level="2" class="topic-meta-data" role="heading"><div class="post-infos"></div></div></div></div></div>  
When the Port 53 is already in Use, you can check this with this command (ubuntu):

Port 53 is being used at your host machine, that's why you can not bind 53 to host.

To find what is using port 53 you can do: `sudo lsof -i -P -n | grep LISTEN`

I'm a 99.9% sure that systemd-resolved is what is listening to port 53.

To solve that you need to edit the `/etc/systemd/resolved.conf` and uncomment DNSStubListener and change it to no, so it looks like this: `DNSStubListener=no`

After that reboot your system or restart the service with `service systemd-resolved restart`

</article></div></div></div></div></section></div></div>