Pihole + dnscrypt = pihole FTL crash

[jfb]

@SUNDraK

when the issue occurred if another service "stole" the port 53, but there was non using it, when FTL crashed/stopped working.

This may be due to DNSCrypt using the port on startup prior to fully reading its configuration file that moves it to port 5333.

A few notes from your debug log - all a reiteration of the reply previously posted by Bucking_Horn:

1. Don't use local as your domain name on the LAN. That's used for multicast DNS and will cause other problems if you have devices that want to use Bonjour or other mDNS.

2. Don't provide Google DNS as a second DNS server. Clients are free to use any DNS available to them, which will result in some DNS traffic bypassing Pi-hole.

Why should Pi-hole be my only DNS server?

Reduced Ad Blocking Capability The main reason you should Pi-hole as your only DNS server is that you will see increased performance in the blocking of ads. If you have two DNS servers (Pi-hole and something else), your network clients may not always query Pi-hole for name resolution. If a query happens to be answered from a non-Pi-hole DNS server, your block lists will not apply (since that DNS server doesn't know about them). All Queries Need To Go Through Pi-hole First Since other DNS se…

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 306 bytes from eth0:192.168.1.2
     Offered IP address: 192.168.1.15
     Server IP address: 192.168.1.2
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      netmask: 255.255.255.0
         router: 192.168.1.2
      default-ttl: 64
      lease-time: 86400 ( 1d )
      server-identifier: 192.168.1.2
      domain-name: "local"
      dns-server: 192.168.1.200
      dns-server: 8.8.8.8
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      --- end of options ---
    
   DHCP packets received on interface lo: 0
   DHCP packets received on interface eth0: 1

You still have multiple IP's assigned to the Pi, only one of which is used for Pi-hole. If this is not intentional, then remove the unused IP.

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.1.15/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
   192.168.1.200/24 matches the IP found in /etc/pihole/setupVars.conf