CasaOS(Zimaboard): Pi-Hole local hostname problem in web browser

[cos]

The issue I am facing:
I have been trying to set up my Zimaboard with pi-hole as a local DNS to have local hostname options for my server.
I can ping my server with nslookup or ping,but when I type the name into the web browser bar, it just looks up the text instead of opening the IP address.

Details about my system:
Zimaboard with CasaOS - Pi-Hole as docker.

Router is Fritzbox 7590AX with local DNS server IP 192.168.178.77 (Zimaboard static IP).

What I have changed since installing Pi-hole:

I changed the DNS settings to go back to my routers DNS server (192.168.178.1).

I use DHCP from my router.

I hope I can achieve adblock/websiteblock with pi-hole and the dashboard shows that it works.

To test the local hostname, I use the local DNS records. I choose server.home.lan as my domain.

I checked my devices and the automatic router DHCP links the IPv4 DNS server to 192.168.178.77 (my Zimaboard).
Now when I open a terminal on my PC and run "nslookup server.home.lan", I get

Server: server.home.lan
Address: 192.168.178.77

Name: server.home.lan
Address: 192.168.178.77

But when I type "server.home.lan" in my browser the words just gets searched by my default engine.
When typing in "nslookup pi.hole", I get

Server: server.home.lan
Address: 192.168.178.77

Name: pi.hole
Address: 0.0.0.0

"pi.hole/admin" gives nothing in the browser.

What am I missing in my setup? Or did I do something completely wrong?

[rdwebdesign]

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

[cos]

https://tricorder.pi-hole.net/l33xkYbh/

Update: I changed my Zimaboards IP to a new static IP 192.168.178.222 because I didnt like the old static IP being inside the DHCP range.
I have changed everything accordingly and this debug log is done with the new changes. The issue remains unchanged.

[rdwebdesign]

Just to make sure I understood your issue:

1. Apparently you are able to access the web interface using the IP: http://192.168.178.222/admin .
   Is that correct?

2. you are unable to connect using http://server.home.lan/admin and http://pi.hole/admin ?

[cos]

Not quite right.
I have to use (http://)192.168.178.222:8800/admin/ to connect to the pi-hole web interface.
http://pi.hole/admin does not work for me.
http://server.home.lan/admin is pointing to 192.168.178.222 and by default it should go to port 80 which is my Nginx Proxy Manager "Congratulation" website.

The Port is important because on other ports I have other web interface access for Jellyfin, Portainer and NginxPM.

[rdwebdesign]

You never said before you are using a different port to connect.

Did you try to connect to the web interface using the port?

• http://pi.hole:8800/admin
• http://server.home.lan:8800/admin

[cos]

This http://pi.hole:8800/admin does not work.

"nslookup pi.hole" gives

Server: 192.168.178.222
Address: 192.168.178.222#53
Name: pi.hole
Address: 0.0.0.0

Tho http://server.home.lan:8800/admin does link me with the web interface.

[deHakkelaar]

@cos

Name: pi.hole
Address: 0.0.0.0

pihole -q pi.hole

?

[cos]

This one right?

[Bucking_Horn]

@cos

When typing in "nslookup pi.hole", I get

Server: server.home.lan
Address: 192.168.178.77

Name: pi.hole
Address: 0.0.0.0

You want to set FTLCONF_LOCAL_IPV4 (recommended environment variable) for your Pi-hole container to the IP of the machine hosting Docker. (It's not clear from your output whether that's 192.168.178.77 or 192.168.178.222, or maybe some other IP.)