We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
root@dev-desktop /o/dnscrypt-proxy# ./dnscrypt-proxy -version 2.1.5 root@dev-desktop /o/dnscrypt-proxy# ./dnscrypt-proxy -check [2025-01-04 17:15:24] [NOTICE] dnscrypt-proxy 2.1.5 [2025-01-04 17:15:24] [NOTICE] Source [public-resolvers] loaded [2025-01-04 17:15:24] [NOTICE] Source [relays] loaded [2025-01-04 17:15:24] [NOTICE] Configuration successfully checked root@dev-desktop /o/dnscrypt-proxy# ./dnscrypt-proxy -resolve example.com Resolving [example.com] using 127.0.0.1 port 53 Unable to resolve: [read udp 127.0.0.1:40685->127.0.0.1:53: read: connection refused]
I cant resolve domain during installation by docs https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation-linux
During installation.
root@dev-desktop /o/dnscrypt-proxy# ./dnscrypt-proxy -resolve example.com Resolving [example.com] using 127.0.0.1 port 53 Unable to resolve: [read udp 127.0.0.1:40685->127.0.0.1:53: read: connection refused]
Linux Mint, x86-64:
root@dev-desktop /o/dnscrypt-proxy [1]# inxi -Sx System: Host: dev-desktop Kernel: 6.8.0-38-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 Desktop: Cinnamon v: 6.2.7 Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble
Everything works by sending a first query using dnscrypt-proxy as postulated in documentation for an installation.
dsncrypt-proxy.toml
listen_addresses = ['127.0.0.1:53', '[::1]:53']
resolv.conf
nameserver 127.0.0.1 options edns0
root@dev-desktop /o/dnscrypt-proxy# sudo netstat -tuln | grep ':53' udp 0 0 0.0.0.0:5353 0.0.0.0:* udp6 0 0 :::5353 :::*
dev@dev-desktop /o/dnscrypt-proxy> nslookup example.com 127.0.0.1 Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: example.com Address: 93.184.215.14 Name: example.com Address: 2606:2800:21f:cb07:6820:80da:af6b:8b2c
root@dev-desktop /o/dnscrypt-proxy [1]# ./dnscrypt-proxy -resolve example.com Resolving [example.com] using 127.0.0.1 port 53 Unable to resolve: [read udp 127.0.0.1:57423->127.0.0.1:53: read: connection refused]
dev@dev-desktop /o/dnscrypt-proxy> drill rs.dns-oarc.net TXT ;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 4393 ;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;; rs.dns-oarc.net. IN TXT ;; ANSWER SECTION: ;; AUTHORITY SECTION: dns-oarc.net. 600 IN SOA ns1.dns-oarc.net. hostmaster.dns-oarc.net. 2025010402 300 60 604800 3600 ;; ADDITIONAL SECTION: ;; Query time: 200 msec ;; EDNS: version 0; flags: ; udp: 1232 ;; SERVER: 127.0.0.1 ;; WHEN: Sat Jan 4 19:40:29 2025 ;; MSG SIZE rcvd: 95
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Output of the following commands:
What is affected by this bug?
I cant resolve domain during installation by docs https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation-linux
When does this occur?
During installation.
Where does it happen?
root@dev-desktop /o/dnscrypt-proxy# ./dnscrypt-proxy -resolve example.com Resolving [example.com] using 127.0.0.1 port 53 Unable to resolve: [read udp 127.0.0.1:40685->127.0.0.1:53: read: connection refused]
How do we replicate the issue?
Linux Mint, x86-64:
root@dev-desktop /o/dnscrypt-proxy [1]# inxi -Sx System: Host: dev-desktop Kernel: 6.8.0-38-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 Desktop: Cinnamon v: 6.2.7 Distro: Linux Mint 22 Wilma base: Ubuntu 24.04 noble
Expected behavior (i.e. solution)
Everything works by sending a first query using dnscrypt-proxy as postulated in documentation for an installation.
Other Comments
dsncrypt-proxy.toml
resolv.conf
dev@dev-desktop /o/dnscrypt-proxy> nslookup example.com 127.0.0.1 Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: Name: example.com Address: 93.184.215.14 Name: example.com Address: 2606:2800:21f:cb07:6820:80da:af6b:8b2c
The text was updated successfully, but these errors were encountered: