Wie ist IP-V6-Adresse von pi-hole

[Sonnennutzer]

Wenn ich den IP-V6-Test durchführe, wird nur IP erfolgreich angezeigt. Ich vermute, dass ich die falsche IP-V6-Adresse in der Fritzbox für den lokalen DNS-Server (pi-hole) eingetragen habe. Wo bzw wie kann ich die IP-V6-Adresse von pi-hole ermitteln?

pi-hole selbst zeigt mir allerdings IP-V6-Anfragen im Dashboard an (AAAA)!? Oder ist das was anderes?

Ip-config zeigt mir:

br-9707f086e927: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
inet6 fe80::42:4ff:fec2:9c74 prefixlen 64 scopeid 0x20<link>
ether 02:42:04:c2:9c:74 txqueuelen 0 (Ethernet)
RX packets 28960280 bytes 3786356621 (3.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 33835317 bytes 3185557140 (2.9 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:bd:37:f0:83 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.51 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 fe80::4d10:72f9e14c prefixlen 64 scopeid 0x20<link>
inet6 fd00::dffd:806e:c51a:abfe prefixlen 64 scopeid 0x0<global>
inet6 2003:d6:974f:7900:f311:580f:c1b1:149f prefixlen 64 scopeid 0x0<g lobal>
ether b8:27:eb:3e:38:2a txqueuelen 1000 (Ethernet)
RX packets 31225095 bytes 5113023163 (4.7 GiB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 32691886 bytes 6494265653 (6.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 820609 bytes 85530166 (81.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 820609 bytes 85530166 (81.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth0780b13: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.180.38 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::87e4:63c5:72a0:9581 prefixlen 64 scopeid 0x20<link>
ether 02:97:33:34:63:56 txqueuelen 0 (Ethernet)
RX packets 11 bytes 1863 (1.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 49944 bytes 18867956 (17.9 MiB)
TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0

veth09695b6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.129.37 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::9498fe00:c5c8 prefixlen 64 scopeid 0x20<link>
ether 96:98:17:00:c5:c8 txqueuelen 0 (Ethernet)
RX packets 231 bytes 19733 (19.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 50309 bytes 19290028 (18.3 MiB)
TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0

veth0fdb740: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.59.111 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::986b:4ff:fe31:8332 prefixlen 64 scopeid 0x20<link>
ether 9a:6b:04:31:83:32 txqueuelen 0 (Ethernet)
RX packets 1495532 bytes 198745624 (189.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1512954 bytes 238120065 (227.0 MiB)
TX errors 0 dropped 1 overruns 0 carrier 0 collisions 0

veth426432d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.163.172 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80:eff:fe24:739d prefixlen 64 scopeid 0x20<link>
ether 2a:ac:0e:24:73:9d txqueuelen 0 (Ethernet)
RX packets 346921 bytes 36137256 (34.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 399752 bytes 58143928 (55.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth8e5b24c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.93.164 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::ec65:c62f:c7dc:f5d0 prefixlen 64 scopeid 0x20<link>
ether 96:7c:bc:5e:0e:78 txqueuelen 0 (Ethernet)
RX packets 23369247 bytes 2325184435 (2.1 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 28639959 bytes 2547130036 (2.3 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethb1c5ad9: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.7.83 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::d4f8:ecff:fe44:ade1 prefixlen 64 scopeid 0x20<link>
ether d6:f8:ec:44:ad:e1 txqueuelen 0 (Ethernet)
RX packets 23 bytes 2510 (2.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 49964 bytes 18869591 (17.9 MiB)
TX errors 0 dropped 1 overruns 0 carrier 0 collisions 0

vethdaa11a4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.174.130 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80:b563:f97c:35cb prefixlen 64 scopeid 0x20<link>
ether 06:ec44:8b:76 txqueuelen 0 (Ethernet)
RX packets 332492 bytes 72718722 (69.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 346185 bytes 92464943 (88.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethf892d8d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.10.134 netmask 255.255.0.0 broadcast 169.254.255.255
inet6 fe80::4889:d9ff:feaf:8b8 prefixlen 64 scopeid 0x20<link>
ether 4a:89:d9:af:08:b8 txqueuelen 0 (Ethernet)
RX packets 3415823 bytes 1558990398 (1.4 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3185005 bytes 343538057 (327.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Danke

[Sonnennutzer]

Nun, diese Seite
https://test-ipv6.com/

erklärt es etwas ausführlicher. Es scheint, dass ich nur selbst keine IP-V6-Adresse habe. Obwohl lt. Telekom ich eig. einen haben sollte. Aber piHole mit ipV6 funktioniertscheinbar. Es ist also eine Netzwerksache.