How to Submit a Bug Report

Maintaining security is a top concern

Please report security vulnerabilities in any ISC software to security-officer@isc.org, using our OpenPGP key.

Report non-urgent BIND 9 issues.

Report non-urgent Kea DHCP issues.

Report non-urgent ISC DHCP issues.


Security Issues

DNS and DHCP security are critical to the Internet infrastructure. We appreciate your cooperation, assistance, and initiative in informing us of any bugs you may find in our software. If you think you may be seeing a potential security vulnerability in BIND 9 (for example, a crash with a REQUIRE, INSIST, or ASSERT failure), please report it to us immediately by emailing security-officer@isc.org, using our OpenPGP key to secure your message. Please do not post security vulnerabilities on a public mailing list.

Crashes

If you have a crash, you may want to consult our KB article What to do if your BIND, ISC DHCP, or Kea DHCP server has crashed.

Reporting issues in BIND 9

To report a non-security-related 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 with us via email to info@isc.org. We do not enable new issue creation via email because of the spam problem.

Reporting issues in Kea DHCP

Kea has an open bug database in GitLab. Before opening a new issue, please 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, 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.

Reporting issues in ISC DHCP

ISC DHCP has an open bug database in GitLab. If you previously reported an issue, you may need to re-report it in GitLab. When we migrated to GitLab in March, 2019, we did not migrate the legacy tickets in the old bug database. You are welcome to log feature requests, but at this point, we are unlikely to add new features to ISC DHCP because of the danger of introducing regression bugs. Often it is helpful to post your issue on the dhcp-users mailing list to clarify whether there is already a way to accomplish what you need.

Community support via our open mailing lists

BIND 9, Kea DHCP, 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. Please contact us to find out more about purchasing a support contract and contributing to our development work.


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!