# Top Client / Queries show IPv6 ULA instead of hostname

**URL:** <https://discourse.pi-hole.net/t/top-client-queries-show-ipv6-ula-instead-of-hostname/47994>\
**Category:** Community Help\
**Created:** [July 3, 2021, 6:38pm UTC](https://discourse.pi-hole.net/t/top-client-queries-show-ipv6-ula-instead-of-hostname/47994 "2021-07-03T18:38:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Daxtorim](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/6de8d8/32.png) [@Daxtorim](https://discourse.pi-hole.net/u/Daxtorim)\
**Post date:** [July 3, 2021, 7:54pm UTC](https://discourse.pi-hole.net/t/top-client-queries-show-ipv6-ula-instead-of-hostname/47994/2 "2021-07-03T19:54:07Z")

</div>

> [@Roo](#):
>
> The ULA addresses in question (see first screenshot of top clients) - those do not reverse lookup correctly against my router DNS.

Did you tell Pi-hole to conditionally forward `PTR` queries for those ULAs to your router? If you only filled out the settings page on the dashboard, the ULAs won't be included since Pi-hole will really only conditionally forward queries for the specific (probably IPv4) network you entered there.

To set up conditional forwarding for the ULAs as well (or generally for other networks) you need to create a custom config file. Something specific to each of your subnets or prefixes like this:

```auto
$ cat /etc/dnsmasq.d/conditional_forwarding.conf
# Additional networks for Pi-hole's conditional forwarding
server=/0.8.e.f.ip6.arpa/10.0.0.1
server=/7.6.6.1.f.c.e.f.4.a.d.f.ip6.arpa/10.0.0.1

```

The first pattern is the domain you want to match, the second is pattern is the IP address of the server that should recieve the DNS query, i.e. your router.

Alternatively, `server=/arpa/10.0.0.1` will universally match all `PTR` queries for any prefix or subnet ([and more that's probably handled by your router anyways](https://en.wikipedia.org/wiki/.arpa)).

> [@Roo](#):
>
> However - the doc appears to point to a patch that is supposed to deal with this.

You might have the same problem that I have with my installation:

> [@IP addresses on the dashboard are not replaced by names from the network table if they cannot be associated with a MAC address \*immediately\*](https://discourse.pi-hole.net/t/ip-addresses-on-the-dashboard-are-not-replaced-by-names-from-the-network-table-if-they-cannot-be-associated-with-a-mac-address-immediately/47021):
>
> Expected Behaviour: IP addresses without a known hostname associated to them should be replaced with another hostname of the same device from the network table, if possible. The corresponding setting (NAMES\_FROM\_NETDB) defaults to TRUE. Actual Behaviour: Sometimes IP addresses are not replaced by names from the network table. In the case of the green underlined address, it is already filed under an existing entry which has several known hostnames associated with it. The hostnames ar…

TLDR: There won't be any more attempts after the first one to associate a hostame with any given IPv6 address by default. When there is no _immediate_ mapping of the IPv6 address to a known host in the network table, Pi-hole has no way to know what hostname to use as a replacement from the network table and there won't be any update after that. You have to change this behavior manually by adding `REFRESH_HOSTNAMES=ALL` to _/etc/pihole/pihole-FTL.conf_ in order to have Pi-hole try more than once to update the hostname.

* * *

> [@Roo](#):
>
> I am NOT using the pi-hole DNS, but have configured conditional forwarding to point back to my local DNS run by my router. This is how it is getting the names (at least for ipv4)

I guess you mean Pi-hole's DHCP server here, not DNS, otherwise this makes little sense 🧐 .

---

_[View the full topic](https://discourse.pi-hole.net/t/top-client-queries-show-ipv6-ula-instead-of-hostname/47994)._