Pi-hole and unbound

Source and Details: https://www.kuketz-blog.de


Faster DNS resolving, by becoming own DNS Server


sudo apt install unbound

Create confiig

sudo nano /etc/unbound/unbound.conf.d/pi-hole.conf

Add following content into pi-hole.conf

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

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

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

    # 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!
    # If you use the default dns-root-data package, unbound will find it automatically
    # 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.
    # IP fragmentation is unreliable on the Internet today, and can cause
    # transmission failures when large DNS messages are sent via UDP. Even
    # when fragmentation does work, it may not be secure; it is theoretically
    # possible to spoof parts of a fragmented DNS message, without easy
    # detection at the receiving end. Recently, there was an excellent study
    # >>> Defragmenting DNS - Determining the optimal maximum UDP response size for DNS <<<
    # by Axel Koolhaas, and Tjeerd Slokker (https://indico.dns-oarc.net/event/36/contributions/776/)
    # in collaboration with NLnet Labs explored DNS using real world data from the
    # the RIPE Atlas probes and the researchers suggested different values for
    # IPv4 and IPv6 and in different scenarios. They advise that servers should
    # be configured to limit DNS messages sent over UDP to a size that will not
    # trigger fragmentation on typical network links. DNS servers can switch
    # from UDP to TCP when a DNS response is too big to fit in this limited
    # buffer size. This value has also been suggested in DNS Flag Day 2020.
    edns-buffer-size: 1232

    # 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: fd00::/8
    private-address: fe80::/10

## Performance
# More cache memory, rrset=msg*2 | Default: 4m, 4m
msg-cache-size: 32m
rrset-cache-size: 64m
# Time  to  live [minimum|maximum] for RRsets and messages in the cache | Default: 0, 86400
cache-min-ttl: 3600
cache-max-ttl: 86400
# Serve old responses from cache with a TTL of 0 in the response without waiting for the actual resolution to finish | Default: no, 0
serve-expired: yes
serve-expired-ttl: 86400
# Fetch DNSKEYs earlier (DNSSEC): More cpu usage, less latency | Default: no
prefetch-key: yes
# Helps to reduce the query rate towards targets that get a very high nonexistent name lookup rate | Default: no
aggressive-nsec: yes

## Privacy | Default: no, no
hide-identity: yes
hide-version: yes

EDNS config creation

sudo nano /etc/dnsmasq.d/99-edns.conf

99-ends.conf content


PI-hole adjustment

  • remove on left all hooks
  • add Custom 1 (IPv4):
  • remove Custom 3 (IPv6)
  • active Use DNSSEC in the bottom
  • save

default view


Debian Fix

sudo systemctl disable --now unbound-resolvconf.service
sudo sed -Ei 's/^unbound_conf=/#unbound_conf=/' /etc/resolvconf.conf 
sudo rm /etc/unbound/unbound.conf.d/resolvconf_resolvers.conf

Restart and go live

sudo service unbound restart

PrestaShop Admin Panel 500 error

Issue 1 happened during an update from version to the latest stable one.

After the DB restore, the shop itself run well, but the admin backend run into an error

prestashop FileLocatorFileNotFoundException

solution: download and install the version and copy the src directory from the fresh one, renamed first and deleter afterwards the corrupt one.

Issue 2

Upgrade of modules was not possible: classes/../tools/pear/PEAR.php): failed

solution: removed blockrss module and replaced other corrupted modules which run into the same issues from modules of fresh installation

Prestashop Upgrade Step by Step

Step 1 – Install 1 Click Upgrade module

Step 2 – backup FTP content and database

Step 3 – set the shop into maintenance mode via 1-Click-Upgrade

Step 4 – Start the upgrade

take into account, the module backups it initially
then the copy process starts

Step 5 – Final check after successful upgrade

please act accordingly to last tasks shown in the blue screen

Merge multiple ICS files in one for Outlook import

Prepare all related ics files

  1. Go to calendar and save each relevant event as dedicated ics file (use save as) in one directory

Merge all ics files into one

  1. open command line
  2. navigate to the directory where all your ics files are located
  3. merge them easy together by executing the command copy *.ics all.ics
  1. Open the merged ics files with your favorite editor
  2. Ensure BEGIN:VCALENDAR exists only once at the first event
  3. Remove all other BEGIN:VCALENDAR of other events (use search and replace function)
  4. Ensure END:VCALENDAR exists only once at the end of the file
  5. Remove all other END:VCALENDAR of other events (use search and replace function)
  6. Ensure you have a clean rows between events, without unnecessary space characters:

Fine-tuning of the merged ics before import

If you try to import the ics without fine-tuning, it will not work. Outlook will import only one event. To make it possible, follow the steps below:

Import your final file in your Outlook calendar

  1. Go to file > open and export > import / export
  2. select iCalender (ICS) import as action > next
  3. select your final ics files > import
  4. select dedicated calendar or just import in your current calendar