From www@isc.org Tue Feb 28 09:25:12 2017 MIME-Version: 1.0 X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RP_MATCHES_RCVD,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.0 X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer) content-type: text/plain; charset="utf-8" Message-ID: Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by bugs.isc.org (Postfix) with ESMTP id BF0AA71B5A8 for ; Tue, 28 Feb 2017 09:25:11 +0000 (UTC) Received: from iscwebprod.isc.org (iscwebprod.isc.org [IPv6:2001:4f8:1:d::16]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 2CB72349452 for ; Tue, 28 Feb 2017 09:25:09 +0000 (UTC) Received: from www (uid 80) (envelope-from www@iscwebprod.isc.org) id 7b7d0b by iscwebprod.isc.org (DragonFly Mail Agent v0.11); Tue, 28 Feb 2017 09:25:08 +0000 Delivered-To: bind9-bugs@bugs.isc.org Subject: BIND 9.11.0 - Bind can not start when using LDAP as a dynamic back-end for bind 9.11. Return-Path: X-Original-To: bind9-bugs@bugs.isc.org Date: Tue, 28 Feb 2017 09:25:08 +0000 X-Wpcf7-Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org X-PHP-Originating-Script: 20001:class-phpmailer.php To: bind-bugs@isc.org From: "Arpit Jain" X-RT-Original-Encoding: utf-8 X-RT-Interface: Email Content-Length: 4491 Bug Report from www.isc.org: Name: Arpit Jain Email: arpit.jain9@wipro.com Software Version: BIND 9.11.0 OS: Red Hat Enterprise Linux Server release 6.5 (Santiago) Subject:Bind can not start when using LDAP as a dynamic back-end for bind 9.11. Bug Detail =========== Hello, We are trying to use LDAP as a dynamic back-end for bind 9.11. The LDAP server is at IP: 10.61.216.47 and bind is installed on 10.61.12.130. We are getting the following error while starting named process: Feb 28 09:44:13 vmx0130 named[7383]: starting BIND 9.11.0-P3 Feb 28 09:44:13 vmx0130 named[7383]: running on Linux x86_64 2.6.32-431.75.1.el6.x86_64 #1 SMP Mon Oct 24 16:39:06 EDT 2016 Feb 28 09:44:13 vmx0130 named[7383]: built with '--prefix=/opt/af' '--sysconfdir=/etc/opt/af' '--with-openssl=no' Feb 28 09:44:13 vmx0130 named[7383]: running as: named -c /etc/opt/af/named.conf Feb 28 09:44:13 vmx0130 named[7383]: ---------------------------------------------------- Feb 28 09:44:13 vmx0130 named[7383]: BIND 9 is maintained by Internet Systems Consortium, Feb 28 09:44:13 vmx0130 named[7383]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Feb 28 09:44:13 vmx0130 named[7383]: corporation. Support and training for BIND 9 are Feb 28 09:44:13 vmx0130 named[7383]: available at https://www.isc.org/support Feb 28 09:44:13 vmx0130 named[7383]: ---------------------------------------------------- Feb 28 09:44:13 vmx0130 named[7383]: adjusted limit on open files from 65536 to 1048576 Feb 28 09:44:13 vmx0130 named[7383]: found 4 CPUs, using 4 worker threads Feb 28 09:44:13 vmx0130 named[7383]: using 3 UDP listeners per interface Feb 28 09:44:13 vmx0130 named[7383]: using up to 4096 sockets Feb 28 09:44:13 vmx0130 named[7383]: loading configuration from '/etc/opt/af/named.conf' Feb 28 09:44:13 vmx0130 named[7383]: using default UDP/IPv4 port range: [32768, 61000] Feb 28 09:44:13 vmx0130 named[7383]: using default UDP/IPv6 port range: [32768, 61000] Feb 28 09:44:13 vmx0130 named[7383]: listening on IPv6 interfaces, port 12010 Feb 28 09:44:13 vmx0130 named[7383]: listening on IPv4 interface lo, 127.0.0.1#12010 Feb 28 09:44:13 vmx0130 named[7383]: generating session key for dynamic DNS Feb 28 09:44:13 vmx0130 named[7383]: sizing zone task pool based on 0 zones Feb 28 09:44:13 vmx0130 named[7383]: 'max-cache-size 90%' - setting to 14356MB (out of 15951MB) Feb 28 09:44:13 vmx0130 named[7383]: the key 'rndc-key' is too short to be secure Feb 28 09:44:13 vmx0130 named[7383]: set up managed keys zone for view _default, file 'managed-keys.bind' Feb 28 09:44:13 vmx0130 named[7383]: loading DynDB instance 'my_db_name' driver '/usr/lib64/bind/ldap.so' Feb 28 09:44:13 vmx0130 named[7383]: failed to dynamically load instance 'my_db_name' driver '/usr/lib64/bind/ldap.so': /usr/lib64/bind/ldap.so: undefined symbol: cfg_parse_buffer (failure) Feb 28 09:44:13 vmx0130 named[7383]: dynamic database 'my_db_name' configuration failed: failure Feb 28 09:44:13 vmx0130 named[7383]: loading configuration: failure Feb 28 09:44:13 vmx0130 named[7383]: exiting (due to fatal error) Also, the named.conf file is as follows: masters theMains port 53 { 10.61.12.130; 127.0.0.1; #Used to fool named to allow notifies from localhost (that is the AFRouter) }; acl theMains { 10.61.12.130; }; acl theAssistants { 10.61.12.130; }; acl theAdmins { 10.61.12.130; }; acl theAllServers { theMains; theAssistants; theAdmins; localhost; }; options { directory "/var/opt/af/named"; pid-file "/var/opt/af/run/named.pid"; allow-transfer { theAllServers; }; recursion yes; allow-query { any; }; zone-statistics no; notify yes; max-journal-size 1048576; port 12010; listen-on port 12010 { 127.0.0.1; }; also-notify { 10.61.12.130 port 53; }; }; dyndb my_db_name "/usr/lib64/bind/ldap.so"{ arg uri "ldap://10.61.216.47"; arg "base cn=dns, ou=Daemons, dc=ete.ka.sw.ericsson, dc=se"; arg auth_method "none"; }; logging { channel default_debug { file "data/named.run"; severity dynamic; }; }; controls { inet 127.0.0.1 allow { localhost; theMains; theAdmins; } keys { "rndc-key";}; }; include "/etc/opt/af/rndc.key"; --- This email was received through isc.org Bug Submission Form