Linux client broken when returning from sleep/suspend

I see this on Debian 11 and Pop OS! 20.04 ...

When the systems wake from sleep/suspend, the nextdns client seems broken:

Dec 16 22:18:16 corsair nextdns[1156]: Connected 104.244.209.134:443 (con=28ms tls=30ms, TCP, TLS13)
Dec 16 22:28:17 corsair nextdns[1156]: Connected 104.244.209.134:443 (con=29ms tls=29ms, TCP, TLS13)
Dec 16 22:30:56 corsair nextdns[1156]: Connected 104.244.209.134:443 (con=26ms tls=30ms, TCP, TLS13)
Dec 16 22:32:23 corsair nextdns[1156]: Connected 104.244.209.134:443 (con=27ms tls=29ms, TCP, TLS13)
Dec 17 09:15:22 corsair nextdns[1156]: Query 127.0.0.1 UDP A odrs.gnome.org. (qry=32/res=12) cache fallback HTTP/2.0: doh resolve: dial tcp [2620:11f:7000:1fe::]:443: connect: network is unreachable
Dec 17 09:15:22 corsair nextdns[1156]: Query 127.0.0.1 UDP AAAA odrs.gnome.org. (qry=32/res=12) cache fallback HTTP/2.0: doh resolve: dial tcp 104.244.209.134:443: connect: network is unreachable
Dec 17 09:15:23 corsair nextdns[1156]: Query 127.0.0.1 UDP AAAA mozilla.org. (qry=29/res=12) cache fallback HTTP/2.0: doh resolve: dial tcp 104.244.209.134:443: connect: network is unreachable
Dec 17 09:15:23 corsair nextdns[1156]: Query 127.0.0.1 UDP AAAA detectportal.firefox.com. (qry=42/res=12) cache fallback HTTP/2.0: doh resolve: dial tcp 104.244.209.134:443: connect: network is unreachable
Dec 17 09:15:23 corsair nextdns[1156]: Query 127.0.0.1 UDP A detectportal.firefox.com. (qry=42/res=12) cache fallback HTTP/2.0: doh resolve: dial tcp [2620:11f:7000:1fe::]:443: connect: network is unreachable
Dec 17 09:15:26 corsair nextdns[1156]: Connected 104.244.209.134:443 (con=43ms tls=37ms, TCP, TLS13)
Dec 17 09:16:42 corsair nextdns[1156]: Connected 104.244.209.134:443 (con=31ms tls=37ms, TCP, TLS13)
Dec 17 09:17:26 corsair nextdns[1156]: Received signal: terminated
Dec 17 09:17:26 corsair nextdns[1156]: Stopping NextDNS 1.37.7/linux
Dec 17 09:17:26 corsair systemd[1]: Stopping NextDNS DNS53 to DoH proxy....
Dec 17 09:17:26 corsair nextdns[1156]: Deactivating
Dec 17 09:17:26 corsair nextdns[1156]: NextDNS 1.37.7/linux stopped
Dec 17 09:17:26 corsair systemd[1]: nextdns.service: Succeeded.
Dec 17 09:17:26 corsair systemd[1]: Stopped NextDNS DNS53 to DoH proxy..
Dec 17 09:17:26 corsair systemd[1]: nextdns.service: Consumed 13.702s CPU time.
Dec 17 09:17:26 corsair systemd[1]: Started NextDNS DNS53 to DoH proxy..
Dec 17 09:17:26 corsair nextdns[16562]: Starting NextDNS 1.37.7/linux on localhost:53
Dec 17 09:17:26 corsair nextdns[16562]: Listening on TCP/[::1]:53
Dec 17 09:17:26 corsair nextdns[16562]: Listening on TCP/127.0.0.1:53
Dec 17 09:17:26 corsair nextdns[16562]: Listening on UDP/[::1]:53
Dec 17 09:17:26 corsair nextdns[16562]: Listening on UDP/127.0.0.1:53
Dec 17 09:17:31 corsair nextdns[16562]: Activating
Dec 17 09:17:33 corsair nextdns[16562]: Connected 45.90.28.0:443 (con=26ms tls=91ms, TCP, TLS13)
Dec 17 09:17:33 corsair nextdns[16562]: Connected 104.244.209.134:443 (con=33ms tls=86ms, TCP, TLS13)
Dec 17 09:17:33 corsair nextdns[16562]: Switching endpoint: https://dns.nextdns.io#104.244.209.134,2620:11f:7000:1fe::
Dec 17 09:18:04 corsair nextdns[16562]: Connected 104.244.209.134:443 (con=31ms tls=36ms, TCP, TLS13)

Doing a 'nextdns restart' fixes the problem. It seems like there's not much in the logs, is there a log debug mode or anything?