When DNS caching is enabled, the ISP's DNS does not work properly

### 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

- [X] 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

GitHub releases or script from README

### Setup

On one machine

### AdGuard Home version

v0.107.50

### Action

AdGuardHome IP address: 192.168.5.5
AdGuardHome upstream DNS server is set to 58.20.127.238.
(58.20.127.238 is an ISP DNS.)


### Expected result

DNS caching is disabled.
Using the dig command, DNS resolves normally.
```sh
apline:~# dig @192.168.5.5 jd.com

; <<>> DiG 9.18.24 <<>> @192.168.5.5 jd.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4212
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;jd.com. IN A

;; ANSWER SECTION:
jd.com. 96 IN A 211.144.24.218
jd.com. 96 IN A 211.144.27.126
jd.com. 96 IN A 106.39.171.134
jd.com. 96 IN A 111.13.149.108

;; Query time: 0 msec
;; SERVER: 192.168.5.5#53(192.168.5.5) (UDP)
;; WHEN: Sat Jun 01 18:37:42 CST 2024
;; MSG SIZE rcvd: 99

```

### Actual result

When DNS caching is enabled and using the dig command, DNS cannot resolve.
```sh
apline:~# dig @192.168.5.5 jd.com

; <<>> DiG 9.18.24 <<>> @192.168.5.5 jd.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 24397
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;jd.com. IN A

;; Query time: 2000 msec
;; SERVER: 192.168.5.5#53(192.168.5.5) (UDP)
;; WHEN: Sat Jun 01 18:37:20 CST 2024
;; MSG SIZE rcvd: 24

```

```sh
2024/06/01 18:18:30.691023 [error] dnsproxy: 58.20.127.238:53: response received over udp: "exchanging with 58.20.127.238:53 over udp: read udp 192.168.5.5:50007->58.20.127.238:53: i/o timeout"
```

### Additional information and/or screenshots

```sh
apline:~# nslookup jd.com 58.20.127.238
Server: 58.20.127.238
Address: 58.20.127.238#53

Non-authoritative answer:
Name: jd.com
Address: 211.144.24.218
Name: jd.com
Address: 111.13.149.108
Name: jd.com
Address: 211.144.27.126
Name: jd.com
Address: 106.39.171.134
```
This issue occurs specifically with ISP DNS servers (58.20.127.238, 110.52.127.202)
When using public DNS servers (223.5.5.5, 8.8.8.8), everything works fine
This issue did not occur before; it has only started happening in the last one or two months