Unable to forward request to upstream server

### Prerequisites

- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer

- [X] I have searched other issues and found no duplicates

- [ ] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)

- [X] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)

### Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

### Installation

Docker

### Setup

On one machine

### AdGuard Home version

v0.107.52

### Action

I am planning to migrate my old dns to the new Adguard home.
But when I followed the official guide given and set it up successfully, I was unable to resolve any domains.
I have the upstream servers setup correctly and all are reachable.
I checked the logs through the web but there is no record of requests either, I don't know what the problem is.

The following operations are all on the adguard home server (192.168.0.60):
```sh
adguardhome $ docker run --name adguardhome \
--restart unless-stopped\
-p 53:53/tcp -p 53:53/udp\
-p 67:67/udp -p 68:68/udp\
-p 80:80/tcp -p 443:443/tcp -p 443:443/udp -p 3000:3000/tcp\
-p 853:853/tcp\
-p 784:784/udp -p 853:853/udp -p 8853:8853/udp\
-p 5443:5443/tcp -p 5443:5443/udp\
-v /data/docker/adguardhome/workdir:/opt/adguardhome/work\
-v /data/docker/adguardhome/confdir:/opt/adguardhome/conf\
-d adguard/adguardhome:v0.107.52
2edfe40f2d80c7ca42d738f270b3e6c1c93d8b23073bc78e4fdb45eee0b3a6b9

adguardhome $ tree /data/docker/adguardhome/
/data/docker/adguardhome/
├── confdir
│ ├── AdGuardHome.yaml
│ ├── dns.zz.asia_v2.crt # self-signed certificate
│ └── dns.zz.asia_v2.key # self-signed certificate private key
└── workdir
└── data
├── filters
│ ├── 1725159016.txt
│ └── 1.txt
├── querylog.json
├── sessions.db
└── stats.db

adguardhome $ ss -ntlp
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 4096 0.0.0.0:853 0.0.0.0:* users:(("docker-proxy",pid=5359,fd=4))
LISTEN 0 4096 0.0.0.0:3000 0.0.0.0:* users:(("docker-proxy",pid=5388,fd=4))
LISTEN 0 4096 0.0.0.0:80 0.0.0.0:* users:(("docker-proxy",pid=5306,fd=4))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=863,fd=3))
LISTEN 0 4096 0.0.0.0:53 0.0.0.0:* users:(("docker-proxy",pid=5247,fd=4))
LISTEN 0 4096 0.0.0.0:5443 0.0.0.0:* users:(("docker-proxy",pid=5401,fd=4))
LISTEN 0 4096 192.168.0.60:9100 0.0.0.0:* users:(("node_exporter",pid=2253,fd=3))
LISTEN 0 4096 0.0.0.0:443 0.0.0.0:* users:(("docker-proxy",pid=5320,fd=4))
LISTEN 0 4096 [::]:853 [::]:* users:(("docker-proxy",pid=5366,fd=4))
LISTEN 0 4096 [::]:3000 [::]:* users:(("docker-proxy",pid=5395,fd=4))
LISTEN 0 4096 [::]:80 [::]:* users:(("docker-proxy",pid=5312,fd=4))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=863,fd=4))
LISTEN 0 4096 [::]:53 [::]:* users:(("docker-proxy",pid=5253,fd=4))
LISTEN 0 4096 [::]:5443 [::]:* users:(("docker-proxy",pid=5408,fd=4))
LISTEN 0 4096 [::]:443 [::]:* users:(("docker-proxy",pid=5326,fd=4))
```
Upstream DNS servers:
```sh
adguardhome $ ping -c 4 101.226.4.6
PING 101.226.4.6 (101.226.4.6) 56(84) bytes of data.
64 bytes from 101.226.4.6: icmp_seq=1 ttl=51 time=37.9 ms
64 bytes from 101.226.4.6: icmp_seq=2 ttl=51 time=38.2 ms
64 bytes from 101.226.4.6: icmp_seq=3 ttl=51 time=37.8 ms
64 bytes from 101.226.4.6: icmp_seq=4 ttl=51 time=38.0 ms

--- 101.226.4.6 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 37.811/37.994/38.244/0.156 ms

adguardhome $ ping -c 4 1.0.0.1
PING 1.0.0.1 (1.0.0.1) 56(84) bytes of data.
64 bytes from 1.0.0.1: icmp_seq=1 ttl=52 time=171 ms
64 bytes from 1.0.0.1: icmp_seq=2 ttl=52 time=170 ms
64 bytes from 1.0.0.1: icmp_seq=3 ttl=52 time=170 ms
64 bytes from 1.0.0.1: icmp_seq=4 ttl=52 time=170 ms

--- 1.0.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 170.241/170.472/170.807/0.207 ms

adguardhome $ ping 8.8.4.4 -c 4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_seq=1 ttl=53 time=39.8 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=53 time=42.8 ms
64 bytes from 8.8.4.4: icmp_seq=3 ttl=53 time=39.4 ms
64 bytes from 8.8.4.4: icmp_seq=4 ttl=53 time=79.8 ms

--- 8.8.4.4 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 39.447/50.438/79.755/16.975 ms
```

The following is the result when executed on the client side:
```sh
client $ nslookup -debug -type=a 'www.google.com' 192.168.0.60
;; connection timed out; no servers could be reached

client $ ping 192.168.0.60
PING 192.168.0.60 (192.168.0.60) 56(84) bytes of data.
64 bytes from 192.168.0.60: icmp_seq=1 ttl=64 time=0.162 ms
64 bytes from 192.168.0.60: icmp_seq=2 ttl=64 time=0.149 ms
^C
--- 192.168.0.60 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 0.149/0.155/0.162/0.006 ms

client $ nmap -p 53 192.168.0.60
Starting Nmap 7.92 ( https://nmap.org ) at 2024-09-07 18:47 CST
Nmap scan report for 192.168.0.60
Host is up (0.00021s latency).

PORT STATE SERVICE
53/tcp open domain
MAC Address: 00:0C:29:F4:AE:99 (VMware)

Nmap done: 1 IP address (1 host up) scanned in 0.15 seconds

# other internal dns
client $ nslookup -debug -type=a 'www.google.com' 192.168.0.201
Server: 192.168.0.201
Address: 192.168.0.201#53

------------
QUESTIONS:
www.google.com, type = A, class = IN
ANSWERS:
-> www.google.com
internet address = 31.13.68.169
ttl = 138
AUTHORITY RECORDS:
ADDITIONAL RECORDS:
------------
Non-authoritative answer:
Name: www.google.com
Address: 31.13.68.169
```

### Expected result

Domain name resolution is normal.

### Actual result

```sh
client $ nslookup -debug -type=a 'www.google.com' 192.168.0.60
;; connection timed out; no servers could be reached
```

### Additional information and/or screenshots

```sh
adguardhome $ cat /etc/os-release
NAME="Rocky Linux"
VERSION="9.4 (Blue Onyx)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.4"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Rocky Linux 9.4 (Blue Onyx)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:9::baseos"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2032-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9"
ROCKY_SUPPORT_PRODUCT_VERSION="9.4"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.4"

adguardhome $ getenforce
Disabled

adguardhome $ firewall-cmd --state
not running
```