CoreDNS is developed in the open. Here are some of the channels we use to communicate and contribute.

Mailing list: - discussion around CoreDNS usage, community support and developer discussion (very low traffic, most discussion happens on Github).

Slack: #coredns on

Twitter: @corednsio.

Issue tracker: Use the GitHub issue tracker to file bugs, features request and questions.

Security issue: Send an email to and (optionally) sign using the PGP key with this fingerprint 6A3CF4506D4E7C6BC23CF982258B85CF3880D0F6.

Please do not ask individual project members for support. Use the channels above instead, where the whole community can help you and benefit from the solutions provided.


We welcome community contributions! Please see the file in the CoreDNS repository for instructions on how to submit changes. If you are planning on making more elaborate or controversial changes, please discuss them on the mailing list or on Github before sending a pull request.

Project Governance

CoreDNS is an independent open-source project and not controlled by any single company. To emphasize this and clarify our governance structure, we joined the Cloud Native Computing Foundation in 2017.

Code of Conduct

To make CoreDNS a welcoming and harassment-free experience for everyone, we follow the CNCF Code of Conduct