diff options
| author |  Billie Cleek <bhcleek@users.noreply.github.com>
| 2019-05-01 07:42:38 -0700 |
|---|---|---|
| committer |  Chris O'Haver <cohaver@infoblox.com>
| 2019-05-01 10:42:38 -0400 |
| commit | e178291ed6a9eae5d24bae132b0f4c2f4d75f662 (patch) | |
| tree | b1462a41591bc60b86d4f36b895c851b36695383 /ADOPTERS.md | |
| parent | b4485b48d9d2fdcdac0e2750398b5fe506d3fba4 (diff) | |
| download | coredns-e178291ed6a9eae5d24bae132b0f4c2f4d75f662.tar.gz coredns-e178291ed6a9eae5d24bae132b0f4c2f4d75f662.tar.zst coredns-e178291ed6a9eae5d24bae132b0f4c2f4d75f662.zip | |
kubernetes: never respond with NXDOMAIN for authority label (#2769)
* kubernetes: never respond with NXDOMAIN for authority label
Return a nodata response when trying to resolve the authority's label
for a record type that doesn't match the record type of the authority.
This guards against poisoning the authority record by requesting the
wrong record type for the authority label. For instance, given an
authoritative resolver that uses subdomain delegation for Kubernetes
services of a cluster that's configured to use IPv4, the parent may be
poisoned by querying it for the authority label of the cluster subdomain
with a AAAA record type, which would otherwise (i.e. without this
change) return an NXDOMAIN. That is, given
cluster.example.com NS 10800 ns.dns.cluster.example.com
ns.dns.cluster.example.com A 10800 10.0.1.2
The parent may be poisoned for the SOA TTL by querying it for a AAAA
record of ns.dns.cluster.example.com, causing the parent to fail
delegate properly until the SOA TTL lapses.
* kubernetes: add tests for authority queries
Diffstat (limited to 'ADOPTERS.md')
0 files changed, 0 insertions, 0 deletions