No query log data for either Pi-Hole and AdguardHome

[lbeier]

Describe the bug No query log showing on either Pi-Hole or AdguardHome. Maybe related to boostchicken-dev/udm-utilities/issues/213?

To Reproduce My instances are running on 192.168.3.2. Steps to reproduce the behavior:

1. Run some queries:

   
   ~ » nslookup iad.g.163.com 192.168.3.2
   Server:     192.168.3.2
   Address:    192.168.3.2#53

Non-authoritative answer: Name: iad.g.163.com Address: 0.0.0.0

~ » nslookup google.com 192.168.3.2 Server: 192.168.3.2 Address: 192.168.3.2#53

Non-authoritative answer: Name: google.com Address: 172.217.17.14

2. Install Pi-Hole or AdguardHome
3. Navigate to query log
4. No clients show up other than localhost.

**Expected behavior**
All queries are logged with the IP of the clients.

**Screenshots**

 The Google queries were run from inside UDM:
![Screenshot 2022-01-25 at 14 08 20](https://user-images.githubusercontent.com/607692/150983204-8a52b837-ecf4-4291-9874-e35e232be955.png)

![Screenshot 2022-01-25 at 14 12 47](https://user-images.githubusercontent.com/607692/150983248-1fab6444-3f2c-47ba-ab60-c1909186d1df.png)

**UDM Information**
 - Variant Dream Machine
 - Firmware Version: 1.11.0
 - Controller Version 7.0.18

ubnt-device-info summary

Device information summary: Subsystem ID: ea11 Family: UniFi Dream Machine (UDM) Model: UniFi Dream Machine (UDM) Default MAC address: xx:xx:xx:xx:xx:xx Default IPv4 address: 127.0.0.1 Firmware: 1.11.0 (1.11.0)

**Additional context**
Tested with `adguardhome` as `container` too.

cat /mnt/data/on_boot.d/10-dns.sh

!/bin/sh

configuration variables:

VLAN=5 IPV4_IP="192.168.3.2" IPV4_GW="192.168.3.1/24" IPV6_IP="" IPV6_GW="" FORCED_INTFC="" CONTAINER=pihole

```# cat /mnt/data/podman/cni/20-dns.conflist
{
  "cniVersion": "0.4.0",
  "name": "dns",
  "plugins": [
    {
      "type": "macvlan",
      "mode": "bridge",
      "master": "br5",
      "mac": "<RANDOMLY_GENERATED_MAC_ADDRESS>",
      "ipam": {
        "type": "static",
        "addresses": [
          {
            "address": "192.168.3.2/24",
            "gateway": "192.168.3.1"
          }
        ],
        "routes": [
          {"dst": "0.0.0.0/0"}
        ]
      }
    }
  ]
}```

[lbeier]

The issue was that I had the NextDNS installed. All good now! Sorry for the confusion.