-
```
Checking if DNS resolvers are DNSSEC-verifying...
WARNING: It looks like the DNS resolvers configured on your system do not
verify DNSSEC, or aren't trusted (by having loopback IPs or through…
-
### Summary:
I tried to install a test environment using Docker. It didn't work, and furthermore made global settings changes, including dinghy proxy which installs itself in localStorage on l…
-
Please read contributing guidelines. Thanks.
**Describe the bug**
When browsing instagram or youtube with bypass-lan-china route, I can see quic/udp traffic for http3 in tcpdump from my server.
B…
-
### systemd version the issue has been seen with
255.11
### Used distribution
Gentoo
### Linux kernel version used
6.10.11-stable
### CPU architectures issue was seen on
x86_64, a…
-
### Bug Description
Outgoing UDP messages fail if destination is specified by name, not address, because of a DNS error on the agent.
### Steps to Reproduce
1. Checkout a [Node.js script](htt…
-
### Is this urgent?
No
### Host OS
_No response_
### CPU arch
aarch64
### VPN service provider
ProtonVPN
### What are you using to run the container
docker-compose
### What is the version of…
-
### Search first
- [X] I searched and no similar issues were found
### What Happened?
I would like APP to not use TCP to connect to remote DNS on nodes that don't support UDP, or just not enable DN…
-
### Prerequisites
- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found…
-
Using dns-crypt-proxy with the new configuration results in a "incompatible signature algorithm",
maybe related to the new minisign key ?
[2024-08-07 11:06:09] [NOTICE] dnscrypt-proxy 2.1.5
[20…
-
Users have reported mobile networks where UDP is significantly throttled compared with TCP traffic. (Presumably because all non-QUICK/DNS UDP traffic is bittorrent in the eyes of some netops somewhere…