Please follow the below template, it will help us to help you!
Expected Behaviour:
[ftl online]
Actual Behaviour:
[ftl offline]
Debug Token:
[5kz3rw72ov]
named is running on port 53 and will conflict with Pi-hole. You need to disable that first.
1 Like
disable the port 53? uhm and what do you mean named? my server name you mean?
sorry for asking im just a noob guy here.
You have to disable named, not port 53. Try the following in the terminal on your raspberry pi: killall named, and try starting pihole-FTL again.
Computers use numbered ports to communicate (like lanes on a highway). Port 53 is the DNS port, and Pi-Hole uses that to send and receive the DNS traffic to the clients.
In your case, another process (called "named" - see this link: named(8): Internet domain name server - Linux man page) is using port 53 and Pi-Hole can't use that port.
So, if you stop "named" and keep it from running, then Pi-Hole can use port 53.
What other software are you running on the device that is serving the Pi?
oh i get it now, but actually before you replied, ive already fixed the problem by using another method:
sudo apt-get install git net-tools
git clone --depth 1 GitHub - pi-hole/pi-hole: A black hole for Internet advertisements pi-hole
sudo bash pi-hole/automated\ install/basic-install.sh
with the same fresh installed OS (Ubuntu Server 16.04 32bit)
this method curl -sSL https://install.pi-hole.net | bash, does not work for me.
the named you mention, i think that might be the package that i included when i installed the ubuntu server, something below this image.
hmm btw i get it now. thanks for the support guys. more power
If you selected "DNS server" on that screenshot during installation, default named is installed as part of the BIND9 package.
pi@noads:~ $ apt-file list bind9
bind9: /usr/sbin/named
You can check which daemons are listening on what ports with the netstat command:
pi@noads:~ $ sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 472/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 763/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 26187/dnsmasq
tcp6 0 0 :::80 :::* LISTEN 763/lighttpd
tcp6 0 0 :::53 :::* LISTEN 26187/dnsmasq
udp 0 0 0.0.0.0:53 0.0.0.0:* 26187/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 26187/dnsmasq
udp6 0 0 :::53 :::* 26187/dnsmasq
If your init system is systemd, like most of the current distro's, you can disable named from getting started at boot with below one:
sudo systemctl disable bind9
Or uninstall the BIND9 package like below on apt based systems:
sudo apt-get remove bind9
EDIT: I just now updated Pi-hole to latest V4 and a netstat looks like below now:
pi@noads:~ $ sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 8234/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 8101/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 8234/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 8234/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 8101/lighttpd
tcp6 0 0 :::53 :::* LISTEN 8234/pihole-FTL
udp 0 0 0.0.0.0:53 0.0.0.0:* 8234/pihole-FTL
udp 0 0 0.0.0.0:67 0.0.0.0:* 8234/pihole-FTL
udp6 0 0 :::53 :::* 8234/pihole-FTL
3 Likes
yeah i think i selected it on my first installation setup
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.