No DNS resolution after connecting on Fedora Atomic Desktop

### Please answer the following question for yourself before submitting an issue

- [X] I checked to make sure that this issue has not already been filed

### AdGuard VPN CLI version

v1.1.126

### Environment

- OS: Fedora Linux 40.20241013.0 Atomic Desktop (Kinoite)
- Architecture: x86_64

### Issue Details

Steps to reproduce:
```
user@fedora /v/h/user> curl -fSsL https://raw.githubusercontent.com/AdguardTeam/AdGuardVPNCLI/master/scripts/release/install.sh | sh -s -- -v
Installing AdGuard VPN...
Update channel: release
CPU type: x86_64
Operating system: linux
AdGuard VPN will be installed to '/opt/adguardvpn_cli'
'/opt/adguardvpn_cli' directory does not exist, attempting to create it...
Starting sudo to create directory '/opt/adguardvpn_cli'
'/opt/adguardvpn_cli' has been created and ownership has been set to 'user'
Package name: 'adguardvpn-cli-1.1.126-linux-x86_64.tar.gz'
AdGuard VPN will be installed to '/opt/adguardvpn_cli'
Downloading AdGuard VPN package: https://github.com/AdguardTeam/AdGuardVPNCLI/releases/download/v1.1.126-release/adguardvpn-cli-1.1.126-linux-x86_64.tar.gz
AdGuard VPN package has been downloaded successfully
Checking downloaded package 'adguardvpn-cli-1.1.126-linux-x86_64.tar.gz'
Unpacking package from 'adguardvpn-cli-1.1.126-linux-x86_64.tar.gz' into '/opt/adguardvpn_cli'
Package has been unpacked successfully
Would you like to link the binary to /usr/local/bin? [y/N] y
Binary has been linked to '/usr/local/bin'

To verify the installation, run the following command to import the public key and verify the signature:
gpg --keyserver 'keys.openpgp.org' --recv-key '28645AC9776EC4C00BCE2AFC0FE641E7235E2EC6'
gpg --verify /opt/adguardvpn_cli/adguardvpn-cli.sig /opt/adguardvpn_cli/adguardvpn-cli

AdGuard VPN has been installed successfully!

You can use it by running command:
adguardvpn-cli --help

To enable bash-completion, please add the following line to your shell configuration (~/.bashrc):
[ -s "/opt/adguardvpn_cli/bash-completion.sh" ] && \. "/opt/adguardvpn_cli/bash-completion.sh"
user@fedora /v/h/user> adguardvpn-cli login
Created data directory /home/user/.local/share/adguardvpn-cli
Enter username: *************************
Enter password: *************************
Please enter your 2FA code: *************************
Successfully Logged in
You are now logged in. You can see the list of available locations by running `adguardvpn-cli list-locations`
user@fedora /v/h/user> adguardvpn-cli connect
Would you like to set default routes in TUN mode? This can be changed later in settings (yes/no): yes
Would you allow AdGuard VPN to set system DNS? This can be adjusted later in settings (yes/no): no
To enhance the quality of our application, may we have your permission to collect crash reports? Your feedback is invaluable in helping us improve (yes/no): yes
14.10.2024 20:47:42.349560 INFO [9565] NETWORK_MONITORING get_default_interface: # ip -o route show to default
14.10.2024 20:47:42.351745 INFO [9565] NETWORK_MONITORING get_default_interface: # ip -o route show to default
14.10.2024 20:47:42.357414 INFO [9565] VPNCORE pinger_handler: [0] Using endpoint: name=pbc.agma-analytics.de, address=84.17.55.252:443, relay=none, ping=5ms
14.10.2024 20:47:42.357414 INFO [9565] VPNCORE pinger_handler: [0] Using endpoint: name=pbc.agma-analytics.de, address=84.17.55.252:443, relay=none, ping=5ms
14.10.2024 20:47:42.370124 INFO [9565] VPNCORE raise_state: [0] VPN_SS_CONNECTED
Successfully Connected to WARSAW
You are now connected. You can check the connection status by running `adguardvpn-cli status`
user@fedora /v/h/user> curl https://api.myip.com
curl: (6) Could not resolve host: api.myip.com
user@fedora /v/h/user [6]> dig @1.1.1.1 google.com

; <<>> DiG 9.18.28 <<>> @1.1.1.1 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7698
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
google.com. 26 IN A 142.250.184.238

;; Query time: 70 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Mon Oct 14 20:48:16 CEST 2024
;; MSG SIZE rcvd: 55

user@fedora /v/h/user> ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=255 time=7.09 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=255 time=5.81 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=255 time=5.43 ms
^C
--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 5.430/6.110/7.089/0.709 ms
user@fedora /v/h/user> ping google.com
ping: google.com: Temporary failure in name resolution
user@fedora /v/h/user [2]> adguardvpn-cli status
VPN active, but status unavailable
You can disconnect by running `adguardvpn-cli disconnect`
user@fedora /v/h/user> adguardvpn-cli disconnect
VPN stopped
You are now disconnected. You can connect to a location by running `adguardvpn-cli connect`
user@fedora /v/h/user> curl https://api.myip.com
{"ip":"x.x.x.x","country":"Poland","cc":"PL"}⏎ user@fedora /v/h/user> adguardvpn-cli config show
Current configuration:
Data directory: /home/user/.local/share/adguardvpn-cli
Mode: tun
SOCKS port: 1080
SOCKS host: 127.0.0.1
SOCKS username:
DNS upstream: Default (provided by AdGuard VPN)
Tunnel routing mode: auto
Set system DNS: off
Send crash: on
Update channel: RELEASE
Use QUIC: Default (off)
Show hints: Default (on)
Debug logging: Default (off)
Show notifications: Default (off)
```

AdGuard VPN connection works, but DNS stops working after connecting. I can connect to IPs but no DNS is not working

My DNS settings:

```
[Resolve]
DNS=94.140.14.49#[hidden].d.adguard-dns.com 94.140.14.59#[hidden].d.adguard-dns.com 2a10:50c0:c000::[hidden]#[hidden].d.adguard-dns.com 2a10:50c0:c000::1:[hidden]#[hidden].d.adguard-dns.com
FallbackDNS=94.140.14.49#[hidden].d.adguard-dns.com 94.140.14.59#[hidden].d.adguard-dns.com 2a10:50c0:c000::[hidden]#[hidden].d.adguard-dns.com 2a10:50c0:c000::1:[hidden]#[hidden].d.adguard-dns.com
LLMNR=yes
MulticastDNS=yes
DNSSEC=no
DNSOverTLS=yes
```

I updated from version v1.0 two days ago to version v1.1.126. Before the update, Adguard VPN worked without an issue.

### Expected Behavior

DNS should work when the VPN connections is active

### Actual Behavior

DNS is not working, I am only able to connect to IPs directly.

### Screenshots

Screenshot 1

### Additional Information

I have AdGuard DNS set on router and on computer as well.