-
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
-…
-
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…
-
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…
-
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…
-
### systemd version the issue has been seen with
255.4-1ubuntu8.4
### Used distribution
Ubuntu 24.04 LTS
### Linux kernel version used
6.8.0-49-generic
### CPU architectures issue was seen on
x…
-
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…
-
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
4 months ago
-
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…
-
### systemd version the issue has been seen with
256.5-2ubuntu3 (Ubuntu 24.10)
(and 252.30-1~deb12u2 (Debian 12), 247.3-7+deb11u6 (Debian 11), etc - i.e. this isn't a new regression)
### Used d…
-
### What is the issue?
We had a DNS issue which main symptom was full DNS unreachability (internal/external names):
```
$ nslookup g.co
Server: 100.100.100.100
Address: 100.100.100.100#53
*…