Report BIND issues at
Report ISC DHCP issues at
Report Kea issues at
Report security vulnerabilities to
security-officer at isc.org (see below)
DNS and DHCP security are critical to the Internet Infrastructure. We appreciate your cooperation, assistance and initiative in informing us of the bugs you have found in our software. If you think you may be seeing a potential security vulnerability in BIND (for example, a crash with REQUIRE, INSIST, or ASSERT failure), please report it immediately either by selecting the pull-down to identify it as a security bug on the form below, or by emailing to email@example.com and do not post it on the public mailing list. If you have a crash, you may want to consult ‘What to do if your BIND or DHCP server has crashed.’
Community support via mailing-list
BIND, Kea and ISC DHCP are open source software. Community support is available on our public mailing lists: bind-users, dhcp-users, and kea-users. We also provide expert professional support for our enterprise users via support subscriptions. You can reach our support team by filling out the form at https://www.isc.org/mission/contact/.
Reporting bugs for BIND
To report a bug or request a feature in BIND, please navigate to our Gitlab instance and enter your issue there. You will have the option of marking your issue confidential, if necessary. You will need to create an account on Gitlab, but you can link your credentials from another Gitlab instance or social media account. Once you have logged your issue, you may follow up via email. We don’t want to enable new issue creation via email because of the spam problem.
Reporting bugs for ISC DHCP
To report a bug or documentation error, please submit the Bug Report Form below, or email to firstname.lastname@example.org. You will receive an automated reply from our bug tracking system. Any followup email sent to the ticketing system should use the same subject header, so that it will be routed to the same ticket. If you need to submit attachments, reply to that acknowledgement including your attachments and they will be automatically added to the bug report.
If you wish to submit a feature request, use the form below or email us at email@example.com
As of July 7, 2017 we opened our bug database for guest access at bugs.isc.org. All suggestions submitted will be publicly viewable right away, and bugs submitted will be publicly viewable after triaging. Anonymous guest users will be able to see the issue report, as well as the submitter’s email address and any attachments. If you want us to keep your report confidential, please put “[confidential]” in the subject header or select the confidential option below. If we see that, we will triage your issue into a non-public queue.
Reporting bugs in Kea
Kea has an open bug database at kea.isc.org. Please use the open bug database and look and see if someone has already logged the bug you wish to report. You may be able to add information to an existing report, or to find a workaround or updated status on the issue that impacts you. We also track feature requests in the issue tracker at kea.isc.org, so please submit feature requests there as well. Often it is helpful to first post these requirements on the kea-users mailing list to clarify whether there is already a way to accomplish what you need.
Due to a large ticket backlog and an even larger quantity of incoming spam, we are sometimes slow to respond, especially if a bug is cosmetic or if a feature request is vague or low priority. However, we truly appreciate and depend on community-submitted bug reports and will address all reports of serious defects.
Thank you for your support!