The issue I am facing:
The issue looks like a standard problem, but still, I cant figure out what to do. I moved in to a new place with new router. I have a PiHole which is also used as DHCP-server.
The addressing scheme is 10.0.0.0/24, the routers IP address is x.138. The Pi hole is 10.0.0.1.
It seems to work for some devices, but it does not resolve all of my devices by its name, just showing "unknown" for all of them. (all but one are unknown) Interestingly, it seems like the "unknown" devices don't receive blocking, while the one device which blocks correctly (a Wifi connected Ubuntu notebook) is also resolved.
However, if I look into the settings of "unknown" devices, the seem to know that they rely on the Pi hole for DNS server, since it shows its IP-address.
Details about my system:
In the router, I set the DHCP to the IP-address of my Pi. I did not change the DNS settings.
The /etc/dhcpcd.conf looks like this:
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Allow users of this group to interact with dhcpcd via the control socket.
# Inform the DHCP server of our hostname for DDNS.
# Use the hardware address of the interface for the Client ID.
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
# Persist interface configuration when dhcpcd exits.
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
# Respect the network MTU. This is applied to DHCP routes.
# Most distributions have NTP support.
# A ServerID is required by RFC2131.
# Generate SLAAC address using the Hardware Address of the interface
# OR generate Stable Private IPv6 Addresses based from the DUID
# Example static IP configuration:
#static domain_name_servers=192.168.0.1 22.214.171.124 fd51:42f8:caae:d92e::1
# It is possible to fall back to a static IP if DHCP fails:
# define static profile
# fallback to static profile on eth0
The /etc/pihole/setupVars.conf looks like this:
So I activated the DHCP settings in the Pi Hole, as seen above. I did not actively change something about the IPv6 settings, since I am not sure if I need that (which would be a second, more irrelevant question)
What I have changed since installing Pi-hole:
Nothing but the settings I explained above.