### Author:  [@tomco](https://discourse.pi-hole.net/u/tomco)
#### Post date: [May 22, 2020, 3:50pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/1 "2020-05-22T15:50:35Z")
#### Please follow the below template, it will help us to help you!
### _If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using `nginx` instead of `lighttpd`, or there is some other aspect of your install that is customised) - please use the [Community Help](https://discourse.pi-hole.net/c/bugs-problems-issues/community-help/36) category._
## Expected Behaviour:
The dashboard should display individual client hostnames for each user, as I am using Pihole as my DCHP server with the router's own DCHP server disabled.
Using Raspberry Pi 1 Model B, running Pihole 5.0.
## Actual Behaviour:
The dashboard lists any client using ipv6 to access the network as 'broadband.bt.com'. (see image). This is repeated into the network overview, which seemingly places 'broadband.bt.com' over the device's 'true' hostname (see image), despite this being visible within the DHCP config on the web interface (see image).
## Debug Token:
[https://tricorder.pi-hole.net/pkom1orb8d](https://tricorder.pi-hole.net/pkom1orb8d)
---
### Author:  [@jfb](https://discourse.pi-hole.net/u/jfb)
#### Post date: [May 22, 2020, 3:53pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/2 "2020-05-22T15:53:41Z")
The network table uses the most recent hostname, and if new IPv6 addresses are being created and assigned via the router, then this is what the network table sees.
If you have the ability with your router, disable IPv6 and see if the problem resolves.
---
### Author:  [@tomco](https://discourse.pi-hole.net/u/tomco)
#### Post date: [May 22, 2020, 3:59pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/5 "2020-05-22T15:59:57Z")
Sadly I do not have that ability - my ISP-provided router will not let me turn ipv6 off at all -the only configuration options relating to ipv6 are in the below image.
---
### Author:  [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)
#### Post date: [May 22, 2020, 4:07pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/6 "2020-05-22T16:07:20Z")
> [@Use IPv6 ULA addresses for Pi-hole](https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127):
>
> Many users have reported that frequently changing IPv6 addresses cause page load to be slow or even prevent from working at all. The issues can be fixed by updating the IPv6 address in /etc/pihole/setupVars.conf followed by a run of pihole -g. However, this solution turns out to be very inconvenient since it might be necessary to change the IPv6 address on a regular basis (maybe even multiple times a day). An alternative approach we are currently looking into is the usage of ULA addresses which…
---
### Author:  [@Gijsmilan](https://discourse.pi-hole.net/u/Gijsmilan)
#### Post date: [May 22, 2020, 4:26pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/7 "2020-05-22T16:26:26Z")
Can't you look up the hostname by using the IPv4 address instead of using the most recent hostname found via IPv6? This way the network table would function as wished thus users won't experience the inconvenience.
Edit: to be clear,
using
> dig @(local IP Pi-hole) -x (local IPv4 client) +short
instead of using IPv6:
> dig @(local IP Pi-hole) -x (local IPv6 client) +short
returns the hostname users expect to see.
---
### Author:  [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)
#### Post date: [May 22, 2020, 4:59pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/8 "2020-05-22T16:59:15Z")
>
---
### Author:  [@yubiuser](https://discourse.pi-hole.net/u/yubiuser)
#### Post date: [May 22, 2020, 5:12pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/9 "2020-05-22T17:12:42Z")
The issue is known and worked on, see this topic (again `broadband.bt.com`):
> [@Network table - seeing clients as hostname of router rather than devices](https://discourse.pi-hole.net/t/network-table-seeing-clients-as-hostname-of-router-rather-than-devices/31597):
>
> Pi-hole Version vDev (release/v5.0, v4.3.5-500-gdf13b9c) Web Interface Version vDev (release/v5.0, v4.3.2-498-ge620211) FTL Version vDev (release/v5.0, vDev-a4b26c3) Problem with Beta 5.0: When looking at my network table - lots of the device that rely on the router for their wifi get identified as such (i.e. broadband.bt.com rather than say home-pc). this occurs with a few other devices as well that pass through the home router in some way (ethernet). I've tried flushing the network tabl…
[https://github.com/pi-hole/AdminLTE/commit/3e1a1f59aac82ef2966e08cb21e80f2ac3372efb](https://github.com/pi-hole/AdminLTE/commit/3e1a1f59aac82ef2966e08cb21e80f2ac3372efb)
---
### Author:  [@tomco](https://discourse.pi-hole.net/u/tomco)
#### Post date: [May 22, 2020, 6:37pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/10 "2020-05-22T18:37:54Z")
I don't quite know what this means at all - I'm completely blind to code and everything like this!
---
### Author:  [@tomco](https://discourse.pi-hole.net/u/tomco)
#### Post date: [May 22, 2020, 6:39pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/11 "2020-05-22T18:39:21Z")
Thank you! How would I be able to access that new 'add support for multiple hostnames' feature? Again, I'm blind to code and don't quite understand all this!
---
### Author:  [@yubiuser](https://discourse.pi-hole.net/u/yubiuser)
#### Post date: [May 22, 2020, 6:55pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/12 "2020-05-22T18:55:32Z")
It's part of the `new/mac_clients` branch, [see here](https://discourse.pi-hole.net/t/feedback-for-allow-defining-clients-by-their-mac-address-host-name-and-networking-interface/32324). Please not this branch is still under development and can break things and should be considered as "testing".
Another approach might be to disable IPv6 resolution on pihole.
> [@Network table - seeing clients as hostname of router rather than devices](https://discourse.pi-hole.net/t/network-table-seeing-clients-as-hostname-of-router-rather-than-devices/31597/21):
>
> Well, this sort of exists. Try RESOLVE\_IPV6=no into /etc/pihole/pihole-FTL.conf (create if it does not exist) and restarting with pihole restartdns. Pi-hole will now stop to resolve IPv6 addresses. It may take some minutes (up to an hour) until you see the update on the network table.
---
### Author:  [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)
#### Post date: [May 22, 2020, 7:00pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/13 "2020-05-22T19:00:25Z")
The referenced experimental feature will likely make it only into Pi-hole v5.2 as a lot of additional things may need to get sorted out.
So the issue is that were sourcing host names from the database when there are none or that the IPv6 names overwrite the IPv4 names?
If the former, then we can add a feature to disable this via a config setting for v5.1. If the latter, then @yubiuser's suggestion seems to be the answer here.
---
### Author:  [@tomco](https://discourse.pi-hole.net/u/tomco)
#### Post date: [May 22, 2020, 7:56pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/14 "2020-05-22T19:56:16Z")
Thank you both - and apologies for my unique, annoying network setup. I've moved onto the mentioned testing new/mac\_clients branch for now - and will probably be there until the update moves onto master. I'll check if it offers any sort of solution. The issue was that the generic 'broadband.bt.com' was being used as a hostname for any device using IPv6, rather than the 'true', IPv4 device name - effectively overwriting it as you say.
---
### Author:  [@Gijsmilan](https://discourse.pi-hole.net/u/Gijsmilan)
#### Post date: [May 22, 2020, 8:29pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/16 "2020-05-22T20:29:46Z")
Does this approach only affect the network table (and not the way queries normally work)? Is it just to make Pi-hole resolve hostnames only over IPv4?
---
### Author:  [@yubiuser](https://discourse.pi-hole.net/u/yubiuser)
#### Post date: [May 22, 2020, 8:32pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/17 "2020-05-22T20:32:23Z")
Yes, that's how I understand
> **[Configuration - Pi-hole documentation](https://docs.pi-hole.net/ftldns/configfile/#resolve_ipv6)**
---
### Author:  [@Gijsmilan](https://discourse.pi-hole.net/u/Gijsmilan)
#### Post date: [May 23, 2020, 3:25pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/18 "2020-05-23T15:25:48Z")
Apparently the issue with using RESOLVE\_IPV6=no is that you end up having a network table with a lot of IPv6 adresses without hostname, which is something I cant imagine anyone wants...
---
### Author:  [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)
#### Post date: [May 24, 2020, 8:31pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/19 "2020-05-24T20:31:53Z")
> [@Gijsmilan](#):
>
> you end up having a network table with a lot of IPv6 adresses without hostname, which is something I cant imagine anyone wants
Well, a lot of people seem to don't want the IPv6 host names. This is why we added this option. For instance, many German users receive host names for their IPv6 devices like p200300DA9BBF17FA0000000000000001.dip0.t-ipconnect.de which is their devices IPv6 address transformed into some more or less (rather less...) useful name. I can feel why they want to avoid this.
---
### Author:  [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)
#### Post date: [May 24, 2020, 8:45pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/21 "2020-05-24T20:45:10Z")
> [@DL6ER](#):
>
> we can add a feature to disable this via a config setting for v5.1
Doesn't sound bad to have the option to disable this, so here we go:
>
>
> \*\*By submitting this pull request, I confirm the following:\*\*
>
> \- \[X\] I have re…ad and understood the \[contributors guide\](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md).
> \- \[X\] I have checked that \[another pull request\](https://github.com/pi-hole/FTL/pulls) for this purpose does not exist.
> \- \[X\] I have considered, and confirmed that this submission will be valuable to others.
> \- \[X\] I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
> \- \[X\] I give this submission freely, and claim no ownership to its content.
>
> \*\*How familiar are you with the codebase?:\*\*
>
> \## 10
>
> \---
>
> This adds a new option \`NAMES\_FROM\_NETDB\` which allows to disable the try to obtain an addresses host name using the network table.
>
> One use case it that there is a IPv6 client without a host names itself.
> However, using the network table we can find out that this client is the same device where we also kwon an IPv4 address together with a valid host names for. In this case, we use the host name associated to the other address as this is the same device. This behavior can now be disabled using \`NAMES\_FROM\_NETDB=false\`
>
> This feature has been discussed on Discourse: https://discourse.pi-hole.net/t/incorrect-hostnames/33111
@tomco I'm interested in your thoughts, we should probably open a new discussion when you have suggestions for improving the `new/mac_clients` branch. It is more thought for v5.2, not earlier as there are some more things to get done and I don't want have it sitting as a possible blocker for an intermediate v5.1 release.
---
### Author:  [@Gijsmilan](https://discourse.pi-hole.net/u/Gijsmilan)
#### Post date: [May 25, 2020, 11:21am UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/22 "2020-05-25T11:21:54Z")
> [@Network table - seeing clients as hostname of router rather than devices](https://discourse.pi-hole.net/t/network-table-seeing-clients-as-hostname-of-router-rather-than-devices/31597/21):
>
> RESOLVE\_IPV6=no into /etc/pihole/pihole-FTL.conf
Hmm... I've tried adding RESOLVE\_IPV6=no to /etc/pihole/pihole-FTL.conf, then I used "pihole restartdns" and (just in case) "pihole arpflush". After a few hours of waiting my Pi-hole unfortunately still used IPv6 hostnames. However, it seems like it did stop resolving some IPv6 addresses because there were quite a few of them without hostname. Retried the above steps but with rebooting afterwards but it just won't work. It stills shows the transformed addresses. That's why I commented the above.
Maybe I should just wait until MAC addresses can be used for hostnames...
edit: now the queries page (not the network table) constantly shows the correct hostname for my iPhone, but not for my Windows machine. Maybe the network table just needs to update itself for the iPhone hostname to change. I'll keep waiting.
---
### Author:  [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)
#### Post date: [May 25, 2020, 7:40pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/23 "2020-05-25T19:40:51Z")
> [@Gijsmilan](#):
>
> edit: now the queries page (not the network table) constantly shows the correct hostname for my iPhone, but not for my Windows machine. Maybe the network table just needs to update itself for the iPhone hostname to change. I'll keep waiting.
Thanks, it should work. You can check with `grep "RESOLVE_IPV6" /var/log/pihole-FTL.log` if the setting is used.
---
### Author:  [@Gijsmilan](https://discourse.pi-hole.net/u/Gijsmilan)
#### Post date: [May 26, 2020, 12:32pm UTC](https://discourse.pi-hole.net/t/incorrect-hostnames/33111/24 "2020-05-26T12:32:02Z")
It looks like resolving IPv6 addresses is not disabled. `grep "RESOLVE_IPV6" /var/log/pihole-FTL.log` doesn't return anything and the log file only contains "WARNING: Hostname of client (paste IPv6 GUA) too long, truncating to 64 chars!" and "Resizing "/FTL-queries" from 2064384 to 2293760" and resizing DNS cache.
/etc/pihole/pihole-FTL.conf contains RESOLVE\_IPV6=no and pihole restartdns was used after the modification.
By the way, my queries page decided to change back to an ISP IPv6 address as hostname for the iPhone.
update: I've rebooted the Pi and the log file now shows "RESOLVE\_IPV6: Don't resolve IPv6 addresses" (as expected). However, the lines after the reboot process once again show "WARNING: Hostname of client (paste IPv6 GUA) too long, truncating to 64 chars!", which means FTL is resolving IPv6 addresses? What's happening?
[Next page](https://discourse.pi-hole.net/t/incorrect-hostnames/33111.md?page=2)