samba - Jun 2014 - Forward Samba DC DNS to Bind

I have a running Bind9 infrastructure and intend to have Samba its 
specialities, but leave the bulk to Bind. My idea is to configure a 
slave zone with Samba as master in my top level Bind. However, this 
would need Samba to allow-forward.

Is there any way to configure the internal DNS like that? Or do I have 
to run a Bind instance on the samba machine for that purpose?

Thanks for your help,
- lars.

[global]
dns forwarder= xxx.yyy.zzz

Greetings
 Daniel 

Leitung EDV
Tropenklinik Paul-Lechler-Krankenhaus
Paul-Lechler-Str. 24
72076 T?bingen 
Tel.: 07071/206-463, Fax: 07071/206-499
eMail: mueller at tropenklinik.de
Internet: www.tropenklinik.de




-----Urspr?ngliche Nachricht-----
Von: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org]
Im
Auftrag von Lars Hanke
Gesendet: Freitag, 6. Juni 2014 09:31
An: samba at lists.samba.org
Betreff: [Samba] Forward Samba DC DNS to Bind

I have a running Bind9 infrastructure and intend to have Samba its
specialities, but leave the bulk to Bind. My idea is to configure a slave
zone with Samba as master in my top level Bind. However, this would need
Samba to allow-forward.

Is there any way to configure the internal DNS like that? Or do I have to
run a Bind instance on the samba machine for that purpose?

Thanks for your help,
- lars.
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Hello Lars,

Am 06.06.2014 09:30, schrieb Lars Hanke:
> I have a running Bind9 infrastructure and intend to have Samba its
> specialities, but leave the bulk to Bind. My idea is to configure a
> slave zone with Samba as master in my top level Bind. However, this
> would need Samba to allow-forward.
> 
> Is there any way to configure the internal DNS like that? Or do I have
> to run a Bind instance on the samba machine for that purpose?
Does your BIND runs on the machine that should be the DC? Then you can
use BIND_DLZ to include the AD domain into your existing BIND. It will
handle your existing zones like you had them in the past. And the AD
managed zones, come from AD.

If your existing BIND runs on a different machine, you can do the following:
- Choose if you setup your DC with the internal DNS or BIND_DLZ.
- Then add a forwarder zone in your named.conf for your AD
  domain, pointing to your AD DC(s) DNS:
  zone "samdom.example.com" {
          type forward;
          forwarders { 192.168.1.1; 192.168.1.2; };
  };


Then your clients can use your existing DNS servers and requests for the
AD DNS zone will be forwarded to your DCs.



Regards,
Marc