The issue I am facing: Blocked domains return the IP 0.0.0.0
Details about my system: Docker for Windows, WSL2, Docker container with standard (not-host) networking.
What I have changed since installing Pi-hole: Specified ServerIP (IP of the Windows machine, this IP is not listed in WSL) and VIRTUAL_HOST in docker-compose.yml.
Maybe I'm understanding pi-hole incorrectly, but I thought resources for blocked domains return an empty page/image/etc. But apps like Chrome see the 0.0.0.0 and say the page is unavailable... No ads are nice, but no error pages would be nicer!
ip addr output within WSL2:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 22:b8:63:c9:d3:a7 brd ff:ff:ff:ff:ff:ff
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether de:41:5b:4f:cf:4d brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:15:5d:18:68:c5 brd ff:ff:ff:ff:ff:ff
inet 172.26.112.198/20 brd 172.26.127.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::215:5dff:fe18:68c5/64 scope link
valid_lft forever preferred_lft forever
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
Windows ipconfig:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::fc7c:857c:621f:b846%8
IPv4 Address. . . . . . . . . . . : 192.168.0.10 <-- value used for ServerIP
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.111
Ethernet adapter vEthernet (WSL):
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::7414:b4f3:adde:42e1%30
IPv4 Address. . . . . . . . . . . : 172.26.112.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
I did try using host networking, but then the container was unavailable from other machines on the network.