Bind9 DLZ not resolving _ldap._tcp.dom.tld?
mycroes at gmail.com
Mon Oct 31 01:21:44 MDT 2011
Seems it does work as intended, not sure what prevented it from
working at first. I now have 2 DC's with the DLZ module where the
identifier is just "AD DNS Zone" and they both seem to work just fine.
2011/10/29 Michael Croes <mycroes at gmail.com>:
> Hi Andrew,
> Perhaps if you have time you can do a quick look in Bind changes, because
> you have access to their source repository, right? Would it be an issue not
> being able to add additional zones; would this be different from Windows
> Op 28 okt. 2011 23:53 schreef "Andrew Bartlett" <abartlet at samba.org> het
>> On Fri, 2011-10-28 at 16:26 +0200, Michael Croes wrote:
>> > Dear list,
>> > I solved the 'issue', so here is the 'solution' for future reference:
>> > The dlz line in named.conf needs to contain the dns zone name, not
>> > just any string.
>> I think we need to raise this with the bind folks. As I understand it,
>> this would break us badly, as we would be unable to add additional zones
>> without changing the bind configuration file.
>> Andrew Bartlett
>> Andrew Bartlett http://samba.org/~abartlet/
>> Authentication Developer, Samba Team http://samba.org
More information about the samba-technical