running an ubuntu 18.04.1 VM in Hyper-V on a Windows machine
Point DNS to Pihole IP and internet/ dns requests should resolve
all dns requests timing out from windows machine after pointing dns to pi hole's ip
am able to ping the pi hole ip
requests in the vm are working fine
fyzuofd5vg
Do you see the requests in /var/log/pihole.log? If not, then Pi-hole is not receiving the request, and something is causing the query to not reach Pi-hole (such as an IPTables rule).
No I don't. I see requests from the VM but not the host.
Do you have any suggestions on how to investigate further?
Here is the output of iptables -L -v after following Redirecting... Is this right?
> Chain INPUT (policy ACCEPT 0 packets, 0 bytes) > pkts bytes target prot opt in out source destination > 181 35130 ACCEPT all -- any any anywhere anywhere ctstate RELATED,ESTABLISHED > 6 412 ACCEPT all -- lo any anywhere anywhere > 376 24074 INPUT_direct all -- any any anywhere anywhere > 376 24074 INPUT_ZONES_SOURCE all -- any any anywhere anywhere > 376 24074 INPUT_ZONES all -- any any anywhere anywhere > 2 259 DROP all -- any any anywhere anywhere ctstate INVALID > 217 15047 REJECT all -- any any anywhere anywhere reject-with icmp-host-prohibited > > Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) > pkts bytes target prot opt in out source destination > 0 0 ACCEPT all -- any any anywhere anywhere ctstate RELATED,ESTABLISHED > 0 0 ACCEPT all -- lo any anywhere anywhere > 0 0 FORWARD_direct all -- any any anywhere anywhere > 0 0 FORWARD_IN_ZONES_SOURCE all -- any any anywhere anywhere > 0 0 FORWARD_IN_ZONES all -- any any anywhere anywhere > 0 0 FORWARD_OUT_ZONES_SOURCE all -- any any anywhere anywhere > 0 0 FORWARD_OUT_ZONES all -- any any anywhere anywhere > 0 0 DROP all -- any any anywhere anywhere ctstate INVALID > 0 0 REJECT all -- any any anywhere anywhere reject-with icmp-host-prohibited > > Chain OUTPUT (policy ACCEPT 356 packets, 151K bytes) > pkts bytes target prot opt in out source destination > 356 151K OUTPUT_direct all -- any any anywhere anywhere > > Chain FORWARD_IN_ZONES (1 references) > pkts bytes target prot opt in out source destination > 0 0 FWDI_public all -- eth0 any anywhere anywhere [goto] > 0 0 FWDI_ftl all -- lo any anywhere anywhere [goto] > 0 0 FWDI_public all -- + any anywhere anywhere [goto] > > Chain FORWARD_IN_ZONES_SOURCE (1 references) > pkts bytes target prot opt in out source destination > > Chain FORWARD_OUT_ZONES (1 references) > pkts bytes target prot opt in out source destination > 0 0 FWDO_public all -- any eth0 anywhere anywhere [goto] > 0 0 FWDO_ftl all -- any lo anywhere anywhere [goto] > 0 0 FWDO_public all -- any + anywhere anywhere [goto] > > Chain FORWARD_OUT_ZONES_SOURCE (1 references) > pkts bytes target prot opt in out source destination > > Chain FORWARD_direct (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDI_ftl (1 references) > pkts bytes target prot opt in out source destination > 0 0 FWDI_ftl_log all -- any any anywhere anywhere > 0 0 FWDI_ftl_deny all -- any any anywhere anywhere > 0 0 FWDI_ftl_allow all -- any any anywhere anywhere > 0 0 ACCEPT icmp -- any any anywhere anywhere > > Chain FWDI_ftl_allow (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDI_ftl_deny (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDI_ftl_log (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDI_public (2 references) > pkts bytes target prot opt in out source destination > 0 0 FWDI_public_log all -- any any anywhere anywhere > 0 0 FWDI_public_deny all -- any any anywhere anywhere > 0 0 FWDI_public_allow all -- any any anywhere anywhere > 0 0 ACCEPT icmp -- any any anywhere anywhere > > Chain FWDI_public_allow (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDI_public_deny (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDI_public_log (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDO_ftl (1 references) > pkts bytes target prot opt in out source destination > 0 0 FWDO_ftl_log all -- any any anywhere anywhere > 0 0 FWDO_ftl_deny all -- any any anywhere anywhere > 0 0 FWDO_ftl_allow all -- any any anywhere anywhere > > Chain FWDO_ftl_allow (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDO_ftl_deny (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDO_ftl_log (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDO_public (2 references) > pkts bytes target prot opt in out source destination > 0 0 FWDO_public_log all -- any any anywhere anywhere > 0 0 FWDO_public_deny all -- any any anywhere anywhere > 0 0 FWDO_public_allow all -- any any anywhere anywhere > > Chain FWDO_public_allow (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDO_public_deny (1 references) > pkts bytes target prot opt in out source destination > > Chain FWDO_public_log (1 references) > pkts bytes target prot opt in out source destination > > Chain INPUT_ZONES (1 references) > pkts bytes target prot opt in out source destination > 376 24074 IN_public all -- eth0 any anywhere anywhere [goto] > 0 0 IN_ftl all -- lo any anywhere anywhere [goto] > 0 0 IN_public all -- + any anywhere anywhere [goto] > > Chain INPUT_ZONES_SOURCE (1 references) > pkts bytes target prot opt in out source destination > > Chain INPUT_direct (1 references) > pkts bytes target prot opt in out source destination > > Chain IN_ftl (1 references) > pkts bytes target prot opt in out source destination > 0 0 IN_ftl_log all -- any any anywhere anywhere > 0 0 IN_ftl_deny all -- any any anywhere anywhere > 0 0 IN_ftl_allow all -- any any anywhere anywhere > 0 0 ACCEPT icmp -- any any anywhere anywhere > > Chain IN_ftl_allow (1 references) > pkts bytes target prot opt in out source destination > 0 0 ACCEPT tcp -- any any anywhere anywhere tcp dpt:4711 ctstate NEW > > Chain IN_ftl_deny (1 references) > pkts bytes target prot opt in out source destination > > Chain IN_ftl_log (1 references) > pkts bytes target prot opt in out source destination > > Chain IN_public (2 references) > pkts bytes target prot opt in out source destination > 376 24074 IN_public_log all -- any any anywhere anywhere > 376 24074 IN_public_deny all -- any any anywhere anywhere > 376 24074 IN_public_allow all -- any any anywhere anywhere > 0 0 ACCEPT icmp -- any any anywhere anywhere > > Chain IN_public_allow (1 references) > pkts bytes target prot opt in out source destination > 0 0 ACCEPT tcp -- any any anywhere anywhere tcp dpt:ssh ctstate NEW > 6 312 ACCEPT tcp -- any any anywhere anywhere tcp dpt:http ctstate NEW > 0 0 ACCEPT tcp -- any any anywhere anywhere tcp dpt:domain ctstate NEW > 151 8456 ACCEPT udp -- any any anywhere anywhere udp dpt:domain ctstate NEW > 0 0 ACCEPT udp -- any any anywhere anywhere udp dpt:bootps ctstate NEW > 0 0 ACCEPT udp -- any any anywhere anywhere udp dpt:dhcpv6-server ctstate NEW > > Chain IN_public_deny (1 references) > pkts bytes target prot opt in out source destination > > Chain IN_public_log (1 references) > pkts bytes target prot opt in out source destination > > Chain OUTPUT_direct (1 references) > pkts bytes target prot opt in out source destination
You should consult the VM software on how to open the firewall it sets up so you can communicate with software listening on the VM's ports.
Hi again,
so I am now installing pi hole on a an actual pi running raspbian and having the same issues 
new Debug token: p7dgy1o4hb
Is this a new install of Pi-Hole on a fresh OS install? The install doesn’t look clean - web version is on a different branch.
Other than that, the debug log shows the Pi-Hole is working properly, so the problem appears to lie in the configuration of the Win client.
I switched the branch to a previous version because of some recommendation for another issue to no avail. I just uninstalled and reinstalled wooooooo it works!
Had to use the dhcp server because my router doesn't allow changing ipv6 dns.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.