You are not logged in.
That all looks O.K. - and you still can't resolve while connected to the VPN?
drill google.com
If this leads to the error from above
;; communications error to 127.0.0.53#53: timed out
something's probably wrong with systemd-resolved.
Does your "/etc/systemd/resolved.conf" contains non-comment lines?
Offline
Where is the nextdns.io server entry coming from?
What are the results of
drill google.com # drill ignores resolve and nsswitch and immediately checks /etc/resolv.conf
nslookup google.com # nslookup will honor etc/nsswitch.conf
Offline
In /etc/systemd/resolved.conf, i have thse lines uncommented :
DNS=193.110.81.0#dns0.eu
DNS=2a0f:fc80::#dns0.eu
DNS=185.253.5.0#dns0.eu
DNS=2a0f:fc81::#dns0.eu
DNSOverTLS=yes
Offline
daniel@anarchy: ~ $ drill google.com # drill ignores resolve
Error: error sending query: Could not send or receive, because of network error
I don't have the command nsswitch available
daniel@anarchy: ~ $ nslookup google.com # nslookup
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; no servers could be reached
Offline
Error: error sending query: Could not send or receive, because of network error
ping _gateway
resolvectl query google.com
nsswitch is no command but /etc/nsswitch.conf
Are you btw. spellbound to use systemd-resolved?
I could imagine that whatever script you use to setup the VPN doesn't account for it and can only handle resolv.conf
Offline
In /etc/systemd/resolved.conf, i have thse lines uncommented :
DNS=193.110.81.0#dns0.eu
DNS=2a0f:fc80::#dns0.eu
DNS=185.253.5.0#dns0.eu
DNS=2a0f:fc81::#dns0.eu
DNSOverTLS=yes
You force systemd-resolved to use DNS over TLS (port 953 instead of 53) even with ProtonVPN's internal DNS server (10.2.0.1) which is already protected from third party eavesdropping due to the VPN encryption.
The most likely cause is that ProtonVPN's DNS server can't "speak" DNS over TLS.
Try disabling DNS over TLS by commenting out the "DNSOverTLS=yes" line in "resolved.conf".
Offline
DanyBreizh wrote:In /etc/systemd/resolved.conf, i have thse lines uncommented :
DNS=193.110.81.0#dns0.eu
DNS=2a0f:fc80::#dns0.eu
DNS=185.253.5.0#dns0.eu
DNS=2a0f:fc81::#dns0.eu
DNSOverTLS=yesYou force systemd-resolved to use DNS over TLS (port 953 instead of 53) even with ProtonVPN's internal DNS server (10.2.0.1) which is already protected from third party eavesdropping due to the VPN encryption.
The most likely cause is that ProtonVPN's DNS server can't "speak" DNS over TLS.
Try disabling DNS over TLS by commenting out the "DNSOverTLS=yes" line in "resolved.conf".
I had the same issue and this worked. Thank you!
Offline
Hello, seems to work :
aniel@anarchy: ~ $ drill google.com @10.2.0.1
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 13982
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; google.com. IN A
;; ANSWER SECTION:
google.com. 178 IN A 142.250.179.110
;; AUTHORITY SECTION:
;; ADDITIONAL SECTION:
;; Query time: 6 msec
;; SERVER: 10.2.0.1
;; WHEN: Sun Jul 6 14:40:46 2025
;; MSG SIZE rcvd: 44
daniel@anarchy: ~ $ nslookup google.com
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: google.com
Address: 142.250.179.110
Name: google.com
Address: 2a00:1450:4007:80e::200e
daniel@anarchy: ~ $
Thanks you very much for your support
Offline
Because you're specifically asking the correct DNS server, see https://bbs.archlinux.org/viewtopic.php … 2249454and if that doesn't help https://bbs.archlinux.org/viewtopic.php … 5#p2249435
Offline