Good evening.
I have a short question about ipv6:
My pihole on my raspberry is also the dhcp server. Is it possible to see the ipv6 as it can be seen with the ipv4 addreses from the devices.
Sorry for my bad english.
Please upload a debug log and post just the token that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
noone have a answere?
I may not understand your question. Your screen capture of the dashboard shows that some clients are being reported by IPv6 address.
yes but is it possible to show the name from the devices.
If I only see the IPv6 address I don't know what devices it is.
That may be expected for some IPv6 addresses - could you provide some examples, including the results of respective nslookups?
How you mean examples?
IPv6 addresses from my wifes pc
fe80::1854:4e90:1663:a737
fd00::15b
fd00::1854:4e90:1663:a737
fd00::8d11:7868:1168:da24
fd00::5c49:b172:bbec:28b5
nslookup from my wifes pc to google.at
C:\Users\cornelia>nslookup google.at
Server: pihole.lan
Address: fd00::c889:5f45:5990:6d8e
Nicht autorisierende Antwort:
Name: google.at
Addresses: 2a00:1450:400d:804::2003
172.217.19.99
Sorry, I probably should have been more specific:
I'd be interested in the results of reverse nslookups for some of the IPv6 addresses you are not seeing a name for, e.g.
nslookup fd00::1234:abcd:cafe:9876
You'd have to substitute with an appropriate IPv6 address, of course.
You could also try to set REFRESH_HOSTNAMES=ALL in your /etc/pihole/pihole-FTL.conf. Run pihole restartdns to apply those settings.
thanks for your answere.
When I run nslookup fd00::219d:1c87:a192:2524 from my linuxpc then the output is:
nslookup fd00::219d:1c87:a192:2524
** server can't find 4.2.5.2.2.9.1.a.7.8.c.1.d.9.1.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.f.ip6.arpa: NXDOMAIN
I try REFRESH_HOSTNAMES=ALL
Is that the machine running Pi-hole?
If so, please repeat on a client.
Also, if dig is available (it commonly would be on Linux), it would be preferred to run:
dig -x fd00::219d:1c87:a192:2524
no my pihole runs on a raspberry with ipv4: 192.168.178.222 and ipv6: fd00::c889:5f45:5990:6d8e
output from dig
daniel@danielpc:~$ dig -x fd00::219d:1c87:a192:2524
; <<>> DiG 9.16.1-Ubuntu <<>> -x fd00::219d:1c87:a192:2524
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55714
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;4.2.5.2.2.9.1.a.7.8.c.1.d.9.1.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.f.ip6.arpa. IN PTR
;; Query time: 16 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sa Sep 11 20:06:11 CEST 2021
;; MSG SIZE rcvd: 101
That machine is using a local stub resolver for DNS resolution.
It is unclear what DNS server is ultimately handling that DNS request.
You could try to force dig to use your router:
dig -x fd00::219d:1c87:a192:2524 @192.168.0.1
where you substitute 192.168.0.1 with your router's IP.
1 Like
output
`; <<>> DiG 9.16.1-Ubuntu <<>> -x fd00::219d:1c87:a192:2524 @192.168.178.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4257
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; QUESTION SECTION:
;4.2.5.2.2.9.1.a.7.8.c.1.d.9.1.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.f.ip6.arpa. IN PTR
;; ANSWER SECTION:
4.2.5.2.2.9.1.a.7.8.c.1.d.9.1.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.f.ip6.arpa. 9 IN PTR cornelia-PC.fritz.box.
;; AUTHORITY SECTION:
4.2.5.2.2.9.1.a.7.8.c.1.d.9.1.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.f.ip6.arpa. 9 IN NS fritz.box.
;; ADDITIONAL SECTION:
fritz.box. 9 IN A 192.168.178.1
fritz.box. 9 IN AAAA fd00::9a9b:cbff:fe9b:7fa2
;; Query time: 4 msec
;; SERVER: 192.168.178.1#53(192.168.178.1)
;; WHEN: Sa Sep 11 21:34:44 CEST 2021
;; MSG SIZE rcvd: 183`
I think with your
the problem is solved(I hope so)
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.