Problem

What does not work as expected?

If I create a dyndb zone in LDAP and then try to refer to that zone in /etc/named.conf the bind start/reload fails with:

/etc/named/ipa-options-ext.conf:25: response-policy zone 'rpz.example.com' is not a master or slave zone

Is your problem related to a single DNS zone or a DNS record?

Yes.

Steps to Reproduce

Seems pretty straightforward. I can actually explain how to reproduce if it is not as straightforward as it seems.

Environment

• Plugin version:
  bind-dyndb-ldap-11.6-2.module_el8.5.0+750+c59b186b.x86_64

• Version of BIND:
  bind-pkcs11-9.11.26-6.el8.x86_64

• Distribution and version (i.e. including updates):

LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 8.4.2105
Release:    8.4.2105
Codename:   n/a

• Architecture:
  x86_64.

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

• Include dyndb (dynamic-db) section from configuration file /etc/named.conf:

dyndb "ipa" "/usr/lib64/bind/ldap.so" {
        uri "ldapi://%2fvar%2frun%2fslapd-EXAMPLE-COM.socket";
        base "cn=dns,dc=example,dc=com";
        server_id "server-staging.example.com";
        auth_method "sasl";
        sasl_mech "GSSAPI";
        sasl_user "DNS/server-staging.example.com";
};

• Do you have some other text based or DLZ zones configured?
  No. That is exactly what I am trying to avoid, in fact.

• Do you have some global forwarders configured in BIND configuration file?
  No.

• Do you have some settings in global configuration object in LDAP?
  I don't know. This is a standard FreeIPA configuration. I' not even sure how to export in LDIF.