Learn more about these different git repos.
Other Git URLs
When server_id is not specified in the configuration file, bind-dyndb-ldap will crash when it's trying to parse the configuration:
server_id
named-pkcs11[19546]: cannot parse settings for 'named.conf for database dns-ldap': not found named-pkcs11[19546]: dynamic database 'dns-ldap' configuration failed: not found named-pkcs11[19546]: loading configuration: not found named-pkcs11[19546]: exiting (due to fatal error)
This is most likely a regression caused by the API changes. The bug is not present for bind-dyndb-ldap-10.1-1.fc24.x86_64.
/etc/named.conf
systemctl restart named-pkcs11
Plugin version: bind-dyndb-ldap-11.1-1.fc27.x86_64
Version of BIND: bind-9.11.0-6.P2.fc25.x86_64
Do you use bind-dyndb-ldap as part of FreeIPA installation? This issue happens when using bind-dyndb-ldap standalone, because FreeIPA does specify server_id in the default template.
server_id "";
systemctl start named-pkcs11
Metadata Update from @tkrizek: - Issue tagged with: regression
Metadata Update from @tkrizek: - Issue assigned to tkrizek - Issue priority set to: 2 - Issue set to the milestone: 11.2
Metadata Update from @tkrizek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1436268
Issue linked to Bugzilla: Bug 1436268
master
Metadata Update from @tkrizek: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.