Your debug log indicates your home network has link-local IPv6 connectivity only:
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] free-lesbian-dating.com is NOERROR on lo (::1)
[✓] No IPv6 address available on enp4s0
[✓] free-lesbian-dating.com is NOERROR on wlp3s0 (fe80::<redacted>%wlp3s0)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)
Without public IPv6 connectivity, your network can't reach public IPv6 DNS addresses, including those of OpenDNS, and whenever Pi-hole tries to contact them, that would result in:
That won't do anything, as it's trying to match a URL, and Pi-hole only ever sees domains.
If e.g. a browser accesses https://discourse.pi-hole.net/t/connection-error-has-been-happening-for-a-while-need-assistance/85053?u=swmom, it would send a query for the domain part to Pi-hole, i.e. just discourse.pi-hole.net.
You should rework those rules accordingly.
You also have a few thousand exact match rules for domains similar to r1---sn-25ge7n76.googlevideo.com.
If those would have been created by a third-party tool in an attempt to block ads on youtube, you should be aware that we've seen reports where Pi-hole experience was negatively impacted, as those tools may constantly stop and restart Pi-hole in short succession, in order to add new match rules.