How do I connect Next DNS to a wireguard server?

Hello, I connected Next DNS to the ubuntu cloud server started, but the connection status has not changed "This device is not using NextDNS.
This device is currently using ”Join-stock company Internet ExchangeMSK-IX” as DNS resolver." 

I can't understand why!?

Everything is working correctly

In systemctl status

● nextdns.service - NextDNS DNS53 to DoH proxy.
     Loaded: loaded (/etc/systemd/system/nextdns.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2024-11-17 02:16:27 MSK; 16h ago
   Main PID: 1262 (nextdns)
      Tasks: 7 (limit: 2219)
     Memory: 4.4M
        CPU: 4.649s
     CGroup: /system.slice/nextdns.service
             └─1262 /usr/bin/nextdns run

Nov 17 02:16:27 v165201.hosted-by-vdsina.com systemd[1]: Started NextDNS DNS53 to DoH proxy..
Nov 17 02:16:27 v165201.hosted-by-vdsina.com nextdns[1262]: Starting NextDNS 1.43.5/linux on localhost:53
Nov 17 02:16:27 v165201.hosted-by-vdsina.com nextdns[1262]: Listening on TCP/127.0.0.1:53
Nov 17 02:16:27 v165201.hosted-by-vdsina.com nextdns[1262]: Listening on UDP/127.0.0.1:53
Nov 17 02:16:32 v165201.hosted-by-vdsina.com nextdns[1262]: Activating
Nov 17 02:37:22 v165201.hosted-by-vdsina.com nextdns[1262]: Connected 45.90.28.0:443 (con=1ms tls=11ms, TCP, TLS13)
Nov 17 02:37:22 v165201.hosted-by-vdsina.com nextdns[1262]: Connected 188.172.219.167:443 (con=1ms tls=7ms, TCP, TLS13)
Nov 17 02:37:22 v165201.hosted-by-vdsina.com nextdns[1262]: Switching endpoint: https://dns.nextdns.io#188.172.219.167,45.11.106.155,2a00:11c0:63:350::3,2a12:8d05:100:2f9:5054:ff:fee8:876b
Nov 17 08:18:10 v165201.hosted-by-vdsina.com nextdns[1262]: Connected 188.172.219.167:443 (con=1ms tls=2ms, TCP, TLS13)

In nextdns log:

Nov 17 02:16:27 v165201.hosted-by-vdsina.com systemd[1]: Started NextDNS DNS53 to DoH proxy..
Nov 17 02:16:27 v165201.hosted-by-vdsina.com nextdns[1262]: Starting NextDNS 1.43.5/linux on localhost:53
Nov 17 02:16:27 v165201.hosted-by-vdsina.com nextdns[1262]: Listening on TCP/127.0.0.1:53
Nov 17 02:16:27 v165201.hosted-by-vdsina.com nextdns[1262]: Listening on UDP/127.0.0.1:53
Nov 17 02:16:32 v165201.hosted-by-vdsina.com nextdns[1262]: Activating
Nov 17 02:37:22 v165201.hosted-by-vdsina.com nextdns[1262]: Connected 45.90.28.0:443 (con=1ms tls=11ms, TCP, TLS13)
Nov 17 02:37:22 v165201.hosted-by-vdsina.com nextdns[1262]: Connected 188.172.219.167:443 (con=1ms tls=7ms, TCP, TLS13)
Nov 17 02:37:22 v165201.hosted-by-vdsina.com nextdns[1262]: Switching endpoint: https://dns.nextdns.io#188.172.219.167,45.11.106.155,2a00:11c0:63:350::3,2a12:8d05:100:2f9:5054:ff:fee8:876b
Nov 17 08:18:10 v165201.hosted-by-vdsina.com nextdns[1262]: Connected 188.172.219.167:443 (con=1ms tls=2ms, TCP, TLS13)

My config file /etc/nextdns.conf

max-inflight-requests 256
listen localhost:53
discovery-dns
timeout 5s
control /var/run/nextdns.sock
max-ttl 0s
bogus-priv true
cache-size 0
mdns all
hardened-privacy false
use-hosts true
setup-router false
debug false
log-queries false
auto-activate true
detect-captive-portals false
profile dd6c42
cache-max-age 0s
report-client-info true

dig @127.0.0.1 google.com

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

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

;; ANSWER SECTION:
google.com.        300    IN    A    142.250.179.142

;; Query time: 20 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Sun Nov 17 18:33:56 MSK 2024
;; MSG SIZE  rcvd: 55

Please help me, I do not know why it does not work.
The ports for DNS are all open from the server side, there are no problems!