AdguardHome DNS caching old value from /etc/hosts

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

### Installation

Docker

### Setup

On one machine

### AdGuard Home version

v0.107.55

### Action

Before restarting the adguard docker, /etc/hosts have entry for
172.23.0.5 plex

After restarting the container, i have updated the entry in /etc/hosts
172.23.0.11 plex

If I execute the nslookup or enter the plex in the browser the ip it resolved to 172.23.0.5 instead of 172.23.0.11.
So basically it caching and not refreshing the entries for dynamic data.

If I restart the container, it loads the latest data /etc/hosts available. So need a fix for this to consider the dynamic host entry in /etc/hosts file.

```sh
nslookup plex 192.168.1.2
```

### Expected result

Server: 192.168.1.2
Address: 192.168.1.2#53

Non-authoritative answer:
Name: plex
Address: 172.23.0.11

### Actual result

Server: 192.168.1.2
Address: 192.168.1.2#53

Non-authoritative answer:
Name: plex
Address: 172.23.0.5

### Additional information and/or screenshots