Unbound IPv6?

Hallo

Ich habe Unbound wie folgt konfiguriert:

server:
    # If no logfile is specified, syslog is used
    # logfile: "/var/log/unbound/unbound.log"
    verbosity: 0

    interface: 127.0.0.1
    port: 5335
    do-ip4: yes
    do-udp: yes
    do-tcp: yes

    # May be set to yes if you have IPv6 connectivity
    do-ip6: yes

    # You want to leave this to no unless you have *native* IPv6. With 6to4 and
    # Terredo tunnels your web browser should favor IPv4 for the same reasons
    prefer-ip6: no

    # Use this only when you downloaded the list of primary root servers!
    root-hints: "/var/lib/unbound/root.hints"

    # Trust glue only if it is within the server's authority
    harden-glue: yes

    # Require DNSSEC data for trust-anchored zones, if such data is absent, the zone becomes BOGUS
    harden-dnssec-stripped: yes

    # Don't use Capitalization randomization as it known to cause DNSSEC issues sometimes
    # see https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378 for further details
    use-caps-for-id: no

    # Reduce EDNS reassembly buffer size.
    # Suggested by the unbound man page to reduce fragmentation reassembly problems
    edns-buffer-size: 1472

    # Perform prefetching of close to expired message cache entries
    # This only applies to domains that have been frequently queried
    prefetch: yes

    # One thread should be sufficient, can be increased on beefy machines. In reality for most users running on small networks or on a single machine, it should be unnecessary to seek performance enhancement by increasing num-threads above 1.
    num-threads: 1

    # Ensure kernel buffer is large enough to not lose messages in traffic spikes
    so-rcvbuf: 1m

    # Ensure privacy of local IP ranges
    private-address: 192.168.0.0/16
    private-address: 169.254.0.0/16
    private-address: 172.16.0.0/12
    private-address: 10.0.0.0/8
    private-address: fd00::/8
    private-address: fe80::/10

und in der PI Hole 5.0: als DNS ::1#5353

Es geht dann aber keine IP V6 Adresse :frowning:

was fehlt noch?

hat der Raspberry eine feste IPv6 zugeordnet bekommen und hast du diese in die Config eingetragen?

passt ĂĽberhaupt nicht zu:

https://docs.pi-hole.net/guides/unbound/#configure-pi-hole

server:
    # If no logfile is specified, syslog is used
    # logfile: "/var/log/unbound/unbound.log"
    verbosity: 0

    port: 5353
    do-ip4: yes
    do-udp: yes
    do-tcp: yes

    # May be set to yes if you have IPv6 connectivity
    do-ip6: yes

    # You want to leave this to no unless you have *native* IPv6. With 6to4 and
    # Terredo tunnels your web browser should favor IPv4 for the same reasons
    prefer-ip6: no

    # Use this only when you downloaded the list of primary root servers!
    root-hints: "/var/lib/unbound/root.hints"

    # Trust glue only if it is within the servers authority
    harden-glue: yes

    # Require DNSSEC data for trust-anchored zones, if such data is absent, the zone becomes BOGUS
    harden-dnssec-stripped: yes

    # Don't use Capitalization randomization as it known to cause DNSSEC issues sometimes
    # see https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378 for further details
    use-caps-for-id: no

    # Reduce EDNS reassembly buffer size.
    # Suggested by the unbound man page to reduce fragmentation reassembly problems
    edns-buffer-size: 1472

    # TTL bounds for cache
    cache-min-ttl: 0
    # cache-min-ttl: 3600
    # cache-max-ttl: 86400

    # increase cache to utilize more RAM
    msg-cache-size: 256m
    rrset-cache-size: 512m

    # serve expired entries (but refresh instantly after serving)
    serve-expired: no

    # Perform prefetching of close to expired message cache entries
    # This only applies to domains that have been frequently queried
    prefetch: yes

    # One thread should be sufficient, can be increased on beefy machines
    num-threads: 2

    # Ensure kernel buffer is large enough to not lose messages in traffic spikes
    so-rcvbuf: 2m

    # Ensure privacy of local IP ranges
    private-address: 192.168.0.0/16
    private-address: 169.254.0.0/16
    private-address: 172.16.0.0/12
    private-address: 10.0.0.0/8
    private-address: fd00::/8
    private-address: fe80::/10

Bildschirmfoto zu 2020-05-05 06-50-30

Frage: Hast du Hyperlocal instaliert?

Falls nicht helfen dir diese beiden Anleitungen recht gut weiter.

https://forum.kuketz-blog.de/viewtopic.php?f=42&t=3067

..und fĂĽr den check besuchst du

https://internet.nl/connection/

Viel GlĂĽck :wink:

Danke.

Hier nix eintragen war die Lösung:
# If no logfile is specified, syslog is used
# logfile: "/var/log/unbound/unbound.log"
verbosity: 0
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
port: 5353
do-ip4: yes
do-udp: yes
do-tcp: yes

was ist Hyperlocal ich hab nur unbound Installiert, was bring tdas?

Du ziehst damit die DNS-Root-Zone auf deinen Pi-Hole. :wink:

Wenn sich interface und port in Deiner unbound-Konfiguration wie oben noch von Deinem Eintrag in Pi-holes UI unterscheiden, kann das noch nicht die Lösung sein.

Die Verwendung von Port 5353 führt außerdem u.U. zu unerwünschten Verhalten, da dieser Port standardmässig von mDNS genutzt wird.

1 Like