Resolving .local names [RESOLVED]

[projectje]

The issue I am facing:

I just installed Pi-hole on a PI and configured it as DHCP and turned DHCP in my router off.

On my laptop I type ipconfig/all and I see it (192.168.178.51) popping up as DNS server:

I now have added in "Local DNS Records" 1 line to check if i can resolve this pi-hole uhm pi itself:

• domain: pihole.local
• IP: 192.168.178.51

but it does not resolve, browser gives a 404 when using pihole.local/admin and nslookup gives : non existent domain

Details about my system:

PiHole Installed on a PI 4

---

?

[CallMeCurious]

Pihole should be the only dns server in your list. The nslookup failed because it tried to resolve the name on the public network.

From the same client what do you get it you run nslookup pihole.local 192.168.178.51

[deHakkelaar]

@projectje

domain: pihole.local

Another note, avoid using .local as a search/suffix domain bc it conflicts with mDNS:

RFC 6762: Multicast DNS

[projectje]

I changed it to pihole.lan

[CallMeCurious]

When you point your query to the pihole ( nslookup pihole.lan 192.168.178.51 ) it works as intended. When you don't it goes to an external dns provider which belongs to ZIGGO-INFRA / Vodaphone NL. ( 2001:b88:1002::10 ).

This would indicate a router setting where perhaps the router is not pointing to the pihole or perhaps the router is providing its own DNS servers in addition to what you set. Either way, I would look at your routers settings.

[projectje]

Could be Ip6 related

I could not change the DNS settings since it does not allow to add local adresses therefore DHCP route

Hmmm ... https://community.ziggo.nl/t5/Internet/IPv6-en-Pihole/m-p/1014875 it seems there is no obvious route which refs How to set up IPv6 for Pihole correctly? - #6 by jpgpi250 someone implies to block all incoming and outgoing ipv6 traffic

but does not solve resolving "pihole.lan"

It probably will lead to having to put the router in bridge modus and pushing a seperate server next to it.

[deHakkelaar]

@projectje

Could be Ip6 related

Do you have an option to disable IPv6 on the router?
Preferably for the LAN side only.
Most of the times you wont need IPv6 and can do with IPv4 only.

Pihole not blocking ads

I just now checked on my Samsung phone (Android 11) and cant find any settings either to disable IPv6 entirely or alter IPv6 DNS settings. Maybe I'm lookin at the wrong spot FYI, your router advertises IPv4 DNS server details via the DHCP protocol: $ sudo pihole-FTL dhcp-discover Scanning all your interfaces for DHCP servers [..] dns-server: 10.0.0.2 And most likely the router advertises IPv6 DNS details via IPv6 RA (Router Advertisement): $ rdisc6 eth0 [..] Recursive DNS server …

[projectje]

Like above: no there is no option to disable ipv6 on the server. I read someone blocked all trafiic but this has no effect as depicted in the screenshots above.
ref: https://community.ziggo.nl/t5/Internet/IPv6-en-Pihole/td-p/1014875/page/2

[CallMeCurious]

Just to be thorough, did you clear client caches after the change? They may have been using cache entries.

[projectje]

i ran ipconfig /flushdns / renew ; reboot n times ; resave network ip4 and ip6 (dynamic) settings etc

[CallMeCurious]

Looking at article you linked it sounds like one solution was to add IP Rules to block the IPV6 Traffic and force IPV4. I'm guessing thats what you mentioned did not work.

I found this article where the ziggo provided a user with a new boot file / firmware to disable IPV6. See article here.

Seems like Ziggo really doesn't want its users to have control.

[projectje]

This is fixed with help of https://community.ziggo.nl/t5/Internet/IPv6-en-Pihole/td-p/1014875/page/2

For other persons dropping in here through search engines:

The trick was this:

a. The router does not allow you to fill in any local IP4 addresses when choosing to set your own DNS servers so filling in the pihole server is not possible (c.q. changing this screen) or changing the DNS :
b. However ... since it does not matter which IP4 address you fill in here (because anyways the pi is the DNS server) you can fill in anything in these IP4 fields and then fill in the IP6 fields the values of the GUA (Gloal Unicast Address) of the PI. (run ip -6 addr show). So it is a counter intuitive trick

(the GUA general remark on occasional loss when Ziggo changes and requires to reconfigure is a consequence but logical)

With this configuration it works, clients now get purely the pihole dns servers.