Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add coredns proposal #1100

Merged
merged 5 commits into from
Oct 23, 2017
Merged

Add coredns proposal #1100

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
6d13333
Add coredns proposal for https://github.com/kubernetes/features/issue…
johnbelamaric Sep 19, 2017
57c5c9e
Add some configuration details, note about wildcard queries
johnbelamaric Sep 20, 2017
f8c9841
Add more operational details
johnbelamaric Sep 20, 2017
566693e
Add section on Reverse DNS
johnbelamaric Sep 21, 2017
7d3bbce
Add performance numbers and a note about upgrade
johnbelamaric Oct 20, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add section on Reverse DNS
  • Loading branch information
@johnbelamaric
johnbelamaric committed Sep 21, 2017
commit 566693e81933f526379d0289ee971987c935a5da
17 changes: 17 additions & 0 deletions contributors/design-proposals/network/coredns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,23 @@ their corresponding domains.
}
```

### Reverse DNS

Reverse DNS is supported for Services and Endpoints. It is not for Pods.

You have to configure the reverse zone to make it work. That means knowing the service CIDR and configuring that
ahead of time (until [#25533](https://github.com/kubernetes/kubernetes/issues/25533) is implemented).

Since reverse DNS zones are on classful boundaries, if you have a classless CIDR for your service CIDR
(say, a /12), then you have to widen that to the containing classful network. That leaves a subset of that network
open to the spoofing described in [#125](https://github.com/kubernetes/dns/issues/125); this is to be fixed
in [#1074](https://github.com/coredns/coredns/issues/1074).

PTR spoofing by manual endpoints
([#124](https://github.com/kubernetes/dns/issues/124)) would
still be an issue even with [#1074](https://github.com/coredns/coredns/issues/1074) solved (as it is in kube-dns). This could be resolved in the case
where `pods verified` is enabled but that is not done at this time.

### Deployment and Operations

Typically when deployed for cluster DNS, CoreDNS is managed by a Deployment. The
Expand Down