CentOS 6.2, Samba 4.0.0beta3, Bind 9.9.1-P1.
I have a workking Bind9 installation which includes several different zone
files. Foward and reverse lookups work fine.
When I include
include "/usr/local/samba4/private/named.conf";
in the named.conf, named will no longer start:
Jul 9 15:01:47 s6a named[9857]: samba_dlz: started for DN
DC=test,DC=cornell,DC=edu
Jul 9 15:01:47 s6a named[9857]: samba_dlz: starting configure
Jul 9 15:01:47 s6a named[9857]: samba_dlz: Failed to configure zone
'test.cornell.edu'
Jul 9 15:01:47 s6a named[9857]: loading configuration: already exists
Jul 9 15:01:47 s6a named[9857]: exiting (due to fatal error)
because of a conflict between an already included zone file and the Samba4
domain (test.cornell.edu).
What is the recommended best practice to fix this situation? I don't
believe that I should have to add the offending zone's contents to
dns_update_list; this seems like a hack to me. But then I don't have a lot
of mileage with samba_dnsupdate yet.
Steve
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
