-
Customer reports issues connecting to resources from within the WSL environment on Windows.
- [x] Investigate connecting to IP/CIDR resources from within WSL
- [x] Investigate connecting to DNS re…
-
We currently integrate libunbound to run unbound queries from our own code. This adds unnecessarily complexity in the app, and has caused issues like #1376 and confusion like #1340. Now that we have a…
-
Do not require an external fully recursive resolver to identify all NS/A/AAAA records for domains and zones by implementing one as a DNS client in go.
Possible starting points?
https://godoc.org/g…
-
Split from #18588. The existing DNS stub resolver uses per-query DNS transport that would cause socket descriptor exhaustion. It might be better to have some mechanism for DNS transport to reduce the…
-
In working on #12778 I found there is not an easy way to test more uncommon DNS scenarios where tight control of responses and errors is needed.
For the pure Go stub resolver consider restructuring t…
danp updated
2 months ago
-
This is a meta bug for tracking the status of the issues regarding builtin DNS stub resolver.
- Refabrication
- #16218
- Transport
- #21160
- #23866
- #23873
- #27552
- Labels
-…
-
Now that third party stubs are released as individual packages it would be great if the package included the upstream version range as an install requirements.
Currently the generated stubs contain…
-
CNAME handling is wrong, according to RFC 1034:
> CNAME RRs cause special action in DNS software. When a name server
> fails to find a desired RR in the resource set associated with the
> domain…
-
A non-DELEG-aware ("legacy") validating stub can only use records that carry a non-DELEG DNSSEC signature chain. This seems to be incompatible with the "sharedds" mechanism proposed in the DNSSEC dra…
-
### Component
systemd-resolved
### Is your feature request related to a problem? Please describe
My upstream DNS already does DNSSEC validation and because I'm doing DoT (I trust the server and the…