Bug Reporting

0. Are you unsure what to do?

Please try to follow steps below. If you encounter any problem or something in this page is unclear, don’t hesitate to write an e-mail to freeipa-users list at freeipa-users@redhat.com

1. Why report bugs?

The main purpose of a bug report is to enable us to fix the bug. The most important prerequisite for this is that the report must be complete and understandable.

2. Before you report a bug

Please check the list of well-known bugs and, if possible, try a current release or development snapshot. Please report the bug even if you can’t test latest versions.

3. What we need to know

About your operating system distribution

  • What distribution do you use? E.g. Fedora
  • Which distribution version do you use? E.g. Fedora 17 including latest updates released up to 2013-03-26.
  • Which architecture do you use? E.g. x86_64

About the plugin

  • What plugin version do you use? On RPM based distributions you can use command:

    $ rpm -q bind-dyndb-ldap

About your problem

  • What does not work as expected?

    • E.g. DNS answers with TXT records contain incorrect data.
  • How can we reproduce the problem? Please describe exact steps you did. For example:

    • Add TXT record with value 1234: $ ipa dnsrecord-add example.com test --txt-rec="1234"

    • Dig the value: $ dig -t TXT test.example.com

    • You will see that value retrieved by dig is 123 instead of


  • Do you see any error messages or other suspicious information in logs? E.g. in /var/named/data/named.run or /var/log/messages? Please attach logs (or at least relevant parts) to the bug report.

    • You can use command rndc trace 10 to raise log level.

    • E.g.

      failed to parse RR entry: dn 'idnsname=text,idnsname=example.com,cn=dns,dc=ipa,dc=test': data '1234': syntax error
  • Is your problem related to a single DNS zone or a record?

    • If it is, is there some settings specific for this particular zone? E.g. PTR record synchronization is enabled for this zone.
    • Please send us the data from the specific record or zone. E.g. output from command $ ipa dnszone-show example.com
  • Could you export the DNS database from LDAP and sent it to us?

    • If it is not possible, contact us and we will try to find minimal necessary subset of the database.
    • E.g. $ ldapsearch -Y GSSAPI -b 'cn=dns, dc=ipa, dc=test' > /tmp/dns.ldif
  • For debugging purposes, we recommend you to use tool dig for DNS queries. Usually, the tool is in package bind-utils. Please always attach complete output from from dig, including comment lines on the beginning and the end.

About your configuration

  • Do you use bind-dyndb-ldap as part of FreeIPA installation?

    • If you answered no:
      • Which LDAP server you use? Which version?
  • Which version of BIND do you use? E.g. bind-9.9.2-3.P1.fc17.x86_64

  • Please provide dyndb (or dynamic-db) section from configuration file /etc/named.conf (or equivalent). E.g.

    dyndb "ipa" "/usr/lib64/bind/ldap.so" {
        uri "ldapi://%2fvar%2frun%2fslapd-EXAMPLE-COM.socket";
        base "cn=dns, dc=example,dc=com";
        auth_method "sasl";
        sasl_mech "GSSAPI";
        sasl_user "DNS/ipa.example.com";
        sync_ptr "yes";
        connections "2";
  • Do you have some other text based or DLZ zones configured?

  • Do you have some global forwarders configured in BIND configuration file? (Statements forward and/or forwarders.) E.g.

    options {
            directory "/var/named";
            forward only;
            forwarders {; };
  • Do you have some settings in global configuration object in LDAP? Configuration object is an LDAP object with idnsConfigObject object class in sub-tree denoted by base argument in named.conf.

    • If you answered yes, please export configuration object to LDIF and attach it to the bug report. E.g.

      $ ldapsearch -Y GSSAPI -b 'cn=dns,dc=example,dc=com' '(objectClass=idnsConfigObject)'
      dn: cn=dns,dc=example,dc=com
      objectClass: idnsConfigObject
      objectClass: nsContainer
      objectClass: top
      cn: dns
      idnsAllowSyncPTR: TRUE
      idnsZoneRefresh: 30

4. Where bug reports should go


5. Do you like reading?

Then read the article How to Report Bugs Effectively :-) It will help you to contribute in the future.

This page was heavily inspired by http://gcc.gnu.org/bugs/.