Conditional forwarding redirects 192.168.178.158 to pi.hole

Help
1

I am running 2 Instances of Pi-hole:
v5 on Pi 3B+ as main Device which is being broadcasted as DNS by the FritzBox (192.168.178.88)
v6 on Pi5 for testing and other Projects (192.168.178.158)

After Enabling Conditional forwarding on the main Pi, now every time I enter 192.168.178.158 in my Browser, it gets redirected to https://pi.hole which the Browser cant find. It only works when specifying https://192.168.178.158.
The Conditional forwarding is configured as: 192.168.178.0/24 , 192.168.178.1 , fritz.box.

2

I would guess this because both yours PIs are configured to use pi.hole. On the test pihole you could consider adding a line to /etc/pihole/pihole-FTL.conf for PIHOLE_PTR=HOSTNAME which should make it respond with the assigned hostname.

PIHOLE_PTR=PI.HOLE|HOSTNAME|HOSTNAMEFQDN|NONE (PR #1111, #1164)

Controls whether and how FTL will reply with for address for
which a local interface exists. Valid options are:
• PI.HOLE (the default) respond with pi.hole
• HOSTNAME serve the machine's global hostname
• HOSTNAMEFQDN serve the machine's global hostname as

3

I don't see how Conditional Forwarding would be involved (yet).

This would suggest that entering 192.168.127.158 in your browser would initiate a HTTP session, which get's redirected to HTTPS by a web server.

As the browser then can't resolve pi.hole at all, that would suggest that it uses neither of your Pi-holes for DNS.

Run from the client with the failing browser, what's the output of:

nslookup pi.hole

nslookup flurry.com

Also, 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:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

4

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.