When setting up Samba 4 AD DC to use BIND DNS is it possible to use BIND located on a separate server? Or do you need to run BIND on the same machine as Samba 4 AD DC?
I think it is NO.
If you think about what bind is doing?!: bind needs to read/write in
ex.:/usr/local/samba/private/dns and reads
/usr/local/samba/private/named.conf.
In my case the named conf:
dlz "AD DNS Zone" {
# For BIND 9.8.0
database "dlopen /usr/local/samba/lib/bind9/dlz_bind9.so";
In my production environment I point bind on my samba4 ads to addresses
outside the domain with the forwarder option to another
bind running.
Greetings
Daniel
-----------------------------------------------
EDV Daniel M?ller
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 Gerry Reno
Gesendet: Sonntag, 10. M?rz 2013 14:14
An: samba at lists.samba.org
Betreff: [Samba] Samba 4 AD DC and BIND
When setting up Samba 4 AD DC to use BIND DNS is it possible to use BIND
located on a separate server?
Or do you need to run BIND on the same machine as Samba 4 AD DC?
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
On 03/11/2013 03:52 AM, Daniel M?ller wrote:> I think it is NO. > If you think about what bind is doing?!: bind needs to read/write in > ex.:/usr/local/samba/private/dns and reads > /usr/local/samba/private/named.conf. > In my case the named conf: > dlz "AD DNS Zone" { > # For BIND 9.8.0 > database "dlopen /usr/local/samba/lib/bind9/dlz_bind9.so"; > > In my production environment I point bind on my samba4 ads to addresses > outside the domain with the forwarder option to another > bind running. > > Greetings > Daniel > > > > ----------------------------------------------- > EDV Daniel M?ller > > 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 Gerry Reno > Gesendet: Sonntag, 10. M?rz 2013 14:14 > An: samba at lists.samba.org > Betreff: [Samba] Samba 4 AD DC and BIND > > When setting up Samba 4 AD DC to use BIND DNS is it possible to use BIND > located on a separate server? > > Or do you need to run BIND on the same machine as Samba 4 AD DC? > >Thanks. That is how I ended up setting it up with a forwarder to the existing BIND server in the network.
When I ran the provision I selected BIND9_DLZ. The provision did not prompt me for a DNS forwarder IP. So after the provision finished I entered the DNS forwarder IP manually into smb.conf. Should the provision have prompted for the DNS forwarder IP?
With the BIND9_DLZ backend, bind actually handles the forwarding, so you
will need to set that up in your named conf, something like the following:
options {
forwarders { 192.249.249.1; 192.249.249.3; };
};
Although, some distros break apart the named stuff, so you may need to find
information specific to your distro on this.
Ricky
On Mon, Mar 11, 2013 at 11:30 AM, Gerry Reno <greno at verizon.net> wrote:
> When I ran the provision I selected BIND9_DLZ.
>
> The provision did not prompt me for a DNS forwarder IP.
>
> So after the provision finished I entered the DNS forwarder IP manually
> into smb.conf.
>
> Should the provision have prompted for the DNS forwarder IP?
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>
--
On 03/11/2013 12:53 PM, Ricky Nance wrote:> With the BIND9_DLZ backend, bind actually handles the forwarding, so you will need to set that up in your named conf, > something like the following: > > options { > forwarders { 192.249.249.1; 192.249.249.3; }; > }; > > Although, some distros break apart the named stuff, so you may need to find information specific to your distro on this. > > Ricky > > > On Mon, Mar 11, 2013 at 11:30 AM, Gerry Reno <greno at verizon.net <mailto:greno at verizon.net>> wrote: > > When I ran the provision I selected BIND9_DLZ. > > The provision did not prompt me for a DNS forwarder IP. > > So after the provision finished I entered the DNS forwarder IP manually into smb.conf. > > Should the provision have prompted for the DNS forwarder IP? > >Thanks. That makes sense. So the provision only prompts for the DNS forwarder IP when you select SAMBA_INTERNAL as the DNS backend.
On 11/03/13 16:30, Gerry Reno wrote:> When I ran the provision I selected BIND9_DLZ. > > The provision did not prompt me for a DNS forwarder IP. > > So after the provision finished I entered the DNS forwarder IP manually into smb.conf. > > Should the provision have prompted for the DNS forwarder IP? > >Hi, No, you only require the forwarder in smb.conf if you using the internal DNS. Rowland -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.