inverse
September 26, 2018, 7:59pm
1
I've got pi-hole running on hass.io via the addon functionality. See addon-pi-hole/README.md at v2.0.4 · hassio-addons/addon-pi-hole · GitHub
And I'm using xwrt vortext running on a Netgear R7000.
I followed the instructions to point pi-hole to the DNS server of the R7000's IP exclusively.
and on the router it looks like:
Having also applied the custom dnsmasq rule on the router of
dhcp-option=6,192.168.1.77
Where that IP is the IP of the PI.
Expected Behaviour:
Working ad-blocking
Actual Behaviour:
Non-functional ad-blocking.
Debug Token: 6w1jriubi3
RamSet
September 26, 2018, 8:04pm
3
How is the client looking from a DHCP perspective?
Does it get all the correct settings?
(Should get an IP like 192.168.1.* with gateway 192.168.1.1 and (sole) DNS 192.168.1.77).
inverse
September 27, 2018, 7:27am
4
How can I check? The output of /etc/resolv.conf is
# Generated by NetworkManager
search beachi
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.1
and my IP looks correct.
update
I followed the directions of pointing the dns to the pi-hole and configuring the advanced dns resolution setting for host name validation and it appears to work . I dont get host names, but get local domain resolution but I can live without that.
system
Closed
October 18, 2018, 7:27am
5
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.