How to install Pi-Hole on CasaOS using BigBearCasaOS

BigBearYouTube BigBearVideos
23

Hello
I tried to install pihole on casaos but it says port 53 in use. I followed the instruction on github ( bigbear scripts) but still it doesn want to install. Any suggestion?
thanks
G

24

Can you run?

lsof -i :53

Then post the output.

25

with sudo…

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dnsmasq 1500 dnsmasq 4u IPv4 8456 0t0 UDP *:domain
dnsmasq 1500 dnsmasq 5u IPv4 8457 0t0 TCP *:domain (LISTEN)
dnsmasq 1500 dnsmasq 6u IPv6 8458 0t0 UDP *:domain
dnsmasq 1500 dnsmasq 7u IPv6 8459 0t0 TCP *:domain (LISTEN)

26
  1. Stop the service immediately:
sudo systemctl stop dnsmasq

This command will stop the dnsmasq service for the current session.

To disable the service:

  1. Disable the service from starting on boot:
sudo systemctl disable dnsmasq

Use this command if you don’t want dnsmasq to start automatically when the system boots.

Verify the service is stopped and disabled:

  1. Check the status of the service:
sudo systemctl status dnsmasq

This will give you the current status, indicating whether the service is active or inactive, and whether it’s enabled or disabled.

Optional: Mask the service

  1. Mask the service:
sudo systemctl mask dnsmasq

Masking the service prevents it from being started manually or automatically by other services. Use this if you want to ensure that dnsmasq cannot be started at all without unmasking it first.

Reverse the mask

To unmask the service:

sudo systemctl unmask dnsmasq

This command removes the mask, making it possible to start the service either manually or automatically, depending on whether it’s enabled.

After unmasking, if you wish to restart the service or enable it to start at boot, you can use the following commands:

To start the service:

sudo systemctl start dnsmasq

To enable the service (auto-start at boot):

sudo systemctl enable dnsmasq

Using these commands, you can fully control the dnsmasq service status, whether it’s stopped, started, enabled, disabled, masked, or unmasked.

27

Képernyőkép 2024-05-03 23-03-44
Képernyőkép 2024-05-03 23-03-44919×23 14.1 KB

I got this error message. When I made everything back port 53 was the problem again.

28
  1. Change DNS Servers: If the DNS servers in your /etc/resolv.conf are not responding, you can change them to public DNS servers like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1):
  • Edit /etc/resolv.conf to use Google’s DNS:
nameserver 8.8.8.8
nameserver 8.8.4.4
  • Or Cloudflare’s DNS:
nameserver 1.1.1.1

After editing, try resolving the domain again or pulling the Docker image.

  1. Test DNS Resolution: Try to resolve the Docker registry domain manually to check if DNS is working correctly:
nslookup registry-1.docker.io

or

dig registry-1.docker.io

These commands should return an IP address. If they don’t, there is a DNS resolution problem still.

  1. Restart Docker Service: Sometimes, the problem can be resolved by simply restarting the Docker service:
sudo systemctl restart docker