For previous version (Pi-hole [v5.18.3] FTL [v5.25.2] Web Interface [v5.21]) of PiHole I had setup
IP of Linux server 192.168.1.102
On this Linux, I had installed docker container with PiHole
Next on main router I had setup PiHole as DNS server (192.168.1.102)
I was able to reach ouit website of pihole configuration
After connection of any device to my local network, I obtained IP from DHCP from main router and DNS was set to my linux server with pihole (192.168.1.102)
After update to latest version of PiHole Docker Tag [2025.02.4] Core [v6.0.3] FTL [v6.0.2] Web interface [v6.0.1]
I am able to connect to PiHole website (192.168.1.102:8081) from any device but once I will set up on my devices for instance on laptop DNS to 192.168.1.102, pages cannot be resolved.
Expected Behaviour:
On the laptop I should be able to set up IP address of PiHole as DNS server.
I should be able to reach out google.com
Actual Behaviour:
I am able to connect to PiHole website (192.168.1.102:8081) from any device but once I will set up on my devices for instance on laptop DNS to 192.168.1.102, pages cannot be resolved.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
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:
# DNS Ports
- "53:53/tcp"
- "53:53/udp"
# Uncomment the below if using Pi-hole as your DHCP Server
#- "67:67/udp"
# Default HTTP Port
- "8081:80/tcp"
# Default HTTPs Port. FTL will generate a self-signed certificate
- "44343:443/tcp"
environment:
# Set the appropriate timezone for your location (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones),
TZ: 'Europe/Warsaw'
# Set a password to access the web interface. Not setting one will result in a random password being assigned
FTLCONF_webserver_api_password: '<password>'
# Volumes store your data between container upgrades
volumes:
# For persisting Pi-hole's databases and common configuration file
- '/opt/pihole/etc-pihole:/etc/pihole'
# Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true'
#- '/opt/pihole/etc-dnsmasq.d:/etc/dnsmasq.d'
restart: unless-stopped
As curl demonstrates that Pi-hole's web pages are accessible via its IP address, and as accessing via IP does not involve DNS at all, that would indicate that you should be able to always access Pi-hole's web pages, regardless of DNS servers used.
Are you positive that you cannot open Pi-hole's web page from a machine once you change that machine's DNS server to your Pi-hole machine's IP?
Those results demonstrate that Pi-hole is generally accessible via 192.168.1.102.
It was used as DNS server for those lookups, has correctly blocked flurry.com, and has succeeded in resolving a public domain.
But your nslookups always show the DNS server as Server: UnKnown, where pi.hole would have been expected.
Together with the timeouts, that would indicate that something is interfering with DNS resolution, either on your network or on the client that ran the nslookups.
You wouldn't run any local firewall or antivirus package on that Windows client, e.g. AVG Secure DNS or AVAST Real-Site?
What do those nslookups return when run from another PC or laptop in your network?
I run the same command on the other laptop where I have installed ESET Endpoint Security but before I executed nslookup I disabled ESET fully.
Result was the same Server: UnKnown
It seems that for Permit all origins and for Respond only on interface, Pi Hole as DNS server is working fine but when I set Allow only local requests it is not working
