I remember the first time I set up Pi-hole. The dashboard looked great, ads were being blocked, but the Top Clients panel showed only my router’s IP address. Every single device in my house was hidden behind one entry. I had no idea which laptop was streaming, which phone was running analytics, or which smart TV was phoning home at 3 AM.
If your Pi-hole clients showing router IP problem is driving you crazy, you are not alone. This is the single most reported Pi-hole configuration issue on the official Discourse forum and on Reddit. The good news is that the fix is straightforward once you understand what is happening. In this guide, I will walk you through why Pi-hole shows only your router instead of individual devices, and the two methods that solve it permanently.
Table of Contents
Why Pi-hole Shows Only the Router IP Instead of Individual Devices?
Pi-hole shows only the router IP because your router is acting as a middleman for every DNS request on your network. When your phone, laptop, or smart TV needs to look up a domain name, it sends the request to the DNS server it learned during its DHCP lease. In most home networks, that DNS server is the router itself.
The router then forwards that request upstream to Pi-hole. When it does this, it uses its own IP address as the source of the request, not the original device. Pi-hole dutifully logs the query, but it only sees the router IP because that is what arrived on its network interface. This is why your Top Clients panel shows a single entry: every query is technically coming from one place.
This happens because most consumer routers have a DNS proxy or DNS relay feature enabled by default. They intercept DNS traffic on port 53 from your devices, forward it to whatever upstream DNS you configured, and rewrite the source address in the process. Pi-hole has no way to see past this rewrite.
Understanding the DNS and DHCP Relationship
To fix this problem, you need to understand two protocols working together. DHCP, the Dynamic Host Configuration Protocol, hands out network settings to devices when they join your network. One of those settings is the DNS server address.
DNS, the Domain Name System, is what translates human-readable names like google.com into IP addresses your devices can actually connect to. Pi-hole is a DNS sinkhole that sits between your devices and the wider internet.
The key insight here is that your router controls what DNS server DHCP hands out to clients. If your router tells every device “I am your DNS server,” the router becomes the bottleneck. We need to change what the router tells devices during DHCP so they talk to Pi-hole directly, skipping the router entirely.
Method 1: Configure Your Router DHCP to Use Pi-hole as DNS
The most common fix is to tell your router’s DHCP service to hand out Pi-hole’s IP address as the DNS server instead of itself. This makes every device on your network query Pi-hole directly, which means Pi-hole sees the actual device IP for every query.
Step-by-Step Instructions
Step 1: Find your Pi-hole IP address. Open the Pi-hole admin dashboard and note the IPv4 address shown on the main page. You will need this for your router configuration. Common addresses look like 192.168.1.100 or 10.0.0.50 depending on your network.
Step 2: Log into your router admin panel. Most routers are accessible at 192.168.1.1 or 192.168.0.1 from a web browser. Check the sticker on your router if you are unsure of the address or login credentials.
Step 3: Locate the DHCP settings. Look for sections labeled LAN, Network, DHCP, or Local Network. Inside, find the DNS server field. Some routers call this “DNS Server 1” or “DNS Addresses.”
Step 4: Replace the existing DNS values with Pi-hole’s IP. Set the primary DNS to your Pi-hole IP address. If your router has a secondary DNS field, you can either leave it blank, set it to a public DNS like 1.1.1.1 as a fallback, or use Pi-hole’s IP again.
Step 5: Save and apply the settings. Most routers require you to click Save or Apply at the bottom of the page. The DHCP service will now hand out Pi-hole as the DNS server to any new or renewing devices.
UniFi Dream Machine Specific Steps
If you run a UniFi Dream Machine or UniFi gateway, the setting lives under Settings, then Networks, then edit your LAN network. Scroll down to DHCP and find “DHCP Name Server.” Set this to “Manual” and enter your Pi-hole IP address. Save the network configuration. UniFi users on the official forum have confirmed this is the cleanest way to restore device visibility.
Mikrotik Specific Steps
Mikrotik routers require extra care because NAT rules can interfere. After setting your Pi-hole IP as the DHCP DNS server, also check your NAT configuration. If you have a masquerade rule on your PPPoE client interface that includes port 53, remove that rule so DNS traffic passes through unmolested. Mikrotik forum users have repeatedly identified this NAT issue as the hidden cause behind persistent router-only Pi-hole logs.
Method 2: Enable Pi-hole DHCP Server Instead
If your router’s DHCP settings are locked, hidden behind ISP firmware, or simply too complicated to navigate, you can disable router DHCP entirely and let Pi-hole handle it instead. Pi-hole has a built-in DHCP server you can enable with a few clicks.
When to Use This Method
Use this method when your ISP router does not let you change DNS settings, when you want Pi-hole to have the final say on every DHCP lease, or when you have already tried Method 1 and devices still show the router. This approach gives Pi-hole complete control over what DNS server new devices receive.
Step-by-Step Instructions
Step 1: Log into Pi-hole admin dashboard and navigate to Settings, then the DHCP tab.
Step 2: Check the box labeled “DHCP server enabled.”
Step 3: Configure your DHCP range. Set the starting and ending IP addresses that Pi-hole will hand out. Use the same range your router was using to avoid disrupting existing leases.
Step 4: Set the router address as the gateway. Pi-hole needs to know where to send traffic that is not local. Enter your router’s IP in the gateway field, often 192.168.1.1 or similar.
Step 5: Save settings, then log into your router and disable its DHCP server. Both services cannot run at the same time on the same network, or you will get conflicting leases.
Trade-offs and Warnings
Be aware that Pi-hole’s DHCP server is simpler than what most routers offer. You will lose features like per-device bandwidth limits, static IP reservations tied to MAC addresses through a friendly interface, and some advanced routing features. For most home users, this is a worthwhile trade. For complex setups, stick to Method 1.
How to Verify Clients Are Now Showing Individually
After making any of the changes above, give your network a few minutes to settle, then open the Pi-hole dashboard. Click on the Top Clients panel or the Query Log. You should now see multiple device IP addresses instead of just your router.
Here is a quick verification checklist. First, confirm Pi-hole shows more than one IP in Top Clients. Second, pick a specific device on your network, open a browser on it, and visit a website. Third, check the Query Log and confirm the entry shows that device’s IP address, not the router’s. Fourth, look for your router’s IP still appearing but for actual router-level queries only, like NTP sync or firmware updates.
If you still see only the router after 10 minutes, devices have not picked up the new DHCP options yet. Move on to the next section.
Why You May Need to Reconnect Devices After DNS Changes
Devices cache their DHCP settings, including the DNS server address, for the duration of their DHCP lease. Even after you change your router’s DHCP DNS settings, existing devices keep using the old DNS server until their lease expires or they reconnect to the network.
Most home routers set DHCP leases for 24 hours. That means after a configuration change, it can take up to a full day before every device picks up the new DNS automatically. To force it immediately, disconnect each device from Wi-Fi and reconnect, reboot the device, or power-cycle your router so all leases are released at once. I usually just reboot the router and wait a few minutes for everything to come back online.
IPv6 Considerations: The Hidden Cause Most Guides Miss
If you have followed all the steps above and Pi-hole is still missing many of your devices, the culprit is almost certainly IPv6. Most modern networks support both IPv4 and IPv6, and devices prefer IPv6 whenever possible. If your router is handing out IPv6 DNS servers that point to itself or to your ISP, those queries will completely bypass Pi-hole.
To check this, open a terminal on one of your devices and run a command like nslookup or dig against an IPv6 address. If the response comes back through your ISP’s DNS, your IPv6 traffic is bypassing Pi-hole entirely. Pi-hole will not see those queries, and worse, they will not be blocked.
The fix depends on your network setup. In UniFi, you can disable IPv6 on the LAN entirely if you do not need it. In other routers, look for IPv6 DHCP settings and either disable them or point them to Pi-hole’s IPv6 address. Pi-hole supports IPv6 natively, so it can be your IPv6 DNS server too. You will need a static IPv6 address for Pi-hole and to configure the router’s IPv6 RA or DHCPv6 to advertise that address.
Router Brand Quick-Reference Table
This table summarizes where to find the DNS settings in the most common router brands. If your router is not listed, the path is usually under LAN, Network, or DHCP settings.
UniFi Dream Machine: Settings, Networks, edit LAN, DHCP Name Server, set Manual, enter Pi-hole IP.
Mikrotik RouterOS: IP, DHCP Server, Networks, set DNS Servers to Pi-hole IP. Also check IP, Firewall, NAT for any rule on port 53.
ASUS (AsusWRT): LAN, DHCP Server, DNS Server 1, set to Pi-hole IP. Optionally set DNS Server 2 as 1.1.1.1 for fallback.
Netgear: Advanced, Setup, Internet, and edit the internet connection to set DNS addresses. Some models hide this under Basic, Internet.
TP-Link: Advanced, Network, DHCP Server, and edit the primary DNS field.
pfSense / OPNsense: Services, DHCP Server, edit LAN, set DNS servers to Pi-hole IP. Apply changes.
Google Nest Wifi: Open Google Home app, tap Wi-Fi, then Advanced Networking, then DNS. Set to Custom and enter Pi-hole IP.
Eero: Open Eero app, Settings, Advanced, DNS. Switch to Manual and enter Pi-hole IP for each node.
Generic ISP router: Look for an option labeled DNS, Primary DNS, or DNS Server in the WAN or Internet section. If locked, consider using Method 2.
Frequently Asked Questions
Why is my Pi-hole only showing my router as a client?
Your router is forwarding DNS queries on behalf of every device on your network. When devices use the router as their DNS server, the router sends queries to Pi-hole using its own IP address as the source, which is why Pi-hole only sees the router in its logs.
How do I configure my router DHCP to use Pi-hole as DNS?
Log into your router admin panel, locate the DHCP or LAN settings, and change the DNS server field from your router’s IP to Pi-hole’s IP address. Save the settings. New and renewing devices will then query Pi-hole directly instead of the router.
Should I use Pi-hole DHCP or router DHCP?
Use router DHCP if you can set the DNS field, because it preserves your router’s other DHCP features like static reservations. Use Pi-hole DHCP if your ISP router locks the DNS settings, since Pi-hole will then handle all leases and DNS assignments itself.
Why do devices not pick up new DNS settings immediately?
Devices cache their DHCP settings, including the DNS server, until their lease expires. Most home routers set 24-hour leases, so it can take a full day before all devices pick up new DNS. Rebooting devices or power-cycling the router forces them to renew immediately.
What is conditional forwarding on Pi-hole and do I need it?
Conditional forwarding tells Pi-hole to send reverse DNS lookups for local IP addresses to your router instead of upstream DNS. Enable it if you want Pi-hole to show device names instead of just IPs in the dashboard. It does not affect regular DNS blocking.
Does IPv6 affect Pi-hole client identification?
Yes. Devices prefer IPv6 when available, and if your router hands out its own IPv6 DNS server, those queries bypass Pi-hole entirely. Either disable IPv6 on your LAN or configure your router to advertise Pi-hole’s IPv6 address as the DNS server.
Final Thoughts
Fixing the Pi-hole clients showing router IP issue comes down to one simple rule: every device on your network needs to talk to Pi-hole directly, not through your router’s DNS relay. Either configure your router DHCP to hand out Pi-hole as the DNS server, or disable router DHCP and let Pi-hole handle it. Add IPv6 to the picture and you have a complete solution.
Once your dashboard starts showing every device on your network, you will finally see what your home network is actually doing. You can spot noisy devices, identify which gadgets are talking to tracking domains, and apply per-device filtering with confidence. That visibility is the real payoff of running Pi-hole, and now you have it.