version: "3"
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
pihole:
container_name: pihole
image: pihole/pihole:latest
# For DHCP it is recommended to remove these ports and instead add: network_mode: "host"
ports:
- "53:53/tcp"
- "53:53/udp"
- "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
- "1010:80/tcp"
- "4443:443/tcp"
environment:
TZ: 'Asia/Kolkata'
# WEBPASSWORD: 'set a secure password here or it will be random'
# Volumes store your data between container upgrades
volumes:
- './etc-pihole:/etc/pihole'
- './etc-dnsmasq.d:/etc/dnsmasq.d'
# https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
cap_add:
- NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed
restart: unless-stopped
Port 53 is used by process user:"named"
Do I need to add the bridge here in pihole network ?
Also the pihole is configured in different port ? Is that the issue ?
Sounds like Windows isn't using the Pi-hole or can even reach a DNS server. Please give more information and follow the Help template which shows when you make a new post, and also post your pihole debug token (just the token URL, not the whole log). That way people can delve into it and help work out what's going on.
That would suggest another DNS resolver on the same machine is already claiming port 53.
You have to prevent that other DNS resolver from doing so, e.g. by disabling or uninstalling it.
On a Linux system, the followong command should help to identify the process that is currently binding port 53:
(Just post the token, please. For your own privacy and security, do not post the full, unsanitised debug log output here. You correctly posted a debug token earlier - I've reinstated that post. )
Did you reverify by rerunning the ss command from above?
It should come back as an empty, headers only list, if stopping and disabling named has been successful.
Upload box and then Generate
)