Pi-hole: Difference between revisions
iwu |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Update Pi-hole == | == Update Pi-hole == | ||
< | <syntaxhighlight lang="console"> | ||
$ pihole - | $ pihole -up | ||
</ | </syntaxhighlight> | ||
== Change web interface admin password == | |||
<syntaxhighlight lang="console"> | |||
$ pihole -a -p | |||
</syntaxhighlight> | |||
== Allow a specific device to bypass Pi-hole completely == | |||
After enabling IPv6, my Nest Hub (2nd gen) was constantly reporting error, or "there was a problem" message, although it would work intermittently. From reading all of the complaints around Google Nest devices and IPv6, I realized it was how DNS request packets were being thrown around. I have Lenovo Smart Display and Google Nest Hub, and Lenovo SD stopped working without IPv6 enabled, so I had a difficult choice to make. Anyway, to make long story short, the solution was to have Nest Hub bypass Pi-hole all together. | |||
Add an entry like this to a new file under <code>/etc/dnsmasq.d/</code>. I named mine <code>07-bypass.conf</code>. | |||
<syntaxhighlight lang="apacheconf"> | |||
dhcp-option=tag:nopieipv6,option6:dns-server,[2606:4700:4700::1111],[2606:4700:4700::1001] | |||
</syntaxhighlight> | |||
Then in another file (e.g. 04-pihole-static-dhcp.conf) have an entry like this. Of course, this also reserves 192.168.86.239 for this particular device. Change the MAC address to your device. You can find the MAC address under Device Information for your Nest device in your Google Home app. | |||
<syntaxhighlight lang="apacheconf"> | |||
dhcp-host=D8:8C:79:4C:BD:93,192.168.86.239,set:nopieipv6,Google-Nest-Hub | |||
</syntaxhighlight> | |||
Latest revision as of 14:52, 13 March 2023
Update Pi-hole
$ pihole -up
Change web interface admin password
$ pihole -a -p
Allow a specific device to bypass Pi-hole completely
After enabling IPv6, my Nest Hub (2nd gen) was constantly reporting error, or "there was a problem" message, although it would work intermittently. From reading all of the complaints around Google Nest devices and IPv6, I realized it was how DNS request packets were being thrown around. I have Lenovo Smart Display and Google Nest Hub, and Lenovo SD stopped working without IPv6 enabled, so I had a difficult choice to make. Anyway, to make long story short, the solution was to have Nest Hub bypass Pi-hole all together.
Add an entry like this to a new file under /etc/dnsmasq.d/. I named mine 07-bypass.conf.
dhcp-option=tag:nopieipv6,option6:dns-server,[2606:4700:4700::1111],[2606:4700:4700::1001]
Then in another file (e.g. 04-pihole-static-dhcp.conf) have an entry like this. Of course, this also reserves 192.168.86.239 for this particular device. Change the MAC address to your device. You can find the MAC address under Device Information for your Nest device in your Google Home app.
dhcp-host=D8:8C:79:4C:BD:93,192.168.86.239,set:nopieipv6,Google-Nest-Hub