-
-
Situation 1: Only one thread can request to upstream.
Situation 2: If timeout after 5s, all request in cache will return SERVFAIL.
@folbricht Can you review my code?
//lockduplicaterequest.go
…
-
Hi, i followed your guide and all was working fine until recently.
Now I cant seem to resolve dns names from the linux box docker-traefik is running on. I keep getting "Temporary failure resolving …
-
### Describe the bug
NixOS declarative containers have a "feature" that overwrites the container's `/etc/resolv.conf` at startup with the one from the host. I have doubts about that implementation …
-
**Is your feature request related to a problem? Please describe.**
Flowroute SRV records are large enough that AWS DNS will not respond with them unless the EDNS flag is set or TCP is used. When…
-
### Operating system
Linux
### System version
Linux 6.6
### Installation type
Original sing-box Command Line
### If you are using a graphical client, please provide the version of the client.
_…
-
**systemd version the issue has been seen with**
> 240
**Used distribution**
> Ubuntu Disco - Server - Nightly Build 2019-02-26, Ubuntu Bionic has this issue too, but is on an old systemd build.…
-
@ookangzheng
1. Do you have TLSA records for your DNS endpoints?
2. You might want to look at The edns-tcp-keepalive EDNS0, as outlined by RFC [7828](https://tools.ietf.org/html/rfc7828), and its i…
obeho updated
3 years ago
-
systemd-resolved determines features that are supported by an upstream DNS resolver and adjusts its query behaviour accordingly. So, for example, if an upstream resolver supports TCP, systemd-resolved…
-
DNSSEC is being deployed.
We should support it eventually.