)
Cc: bind-users@lists.isc.org
Subject: Re: Multiple AD domains
I agree with using BIND as the default DNS server even on Active Directory
environments. Windows DNS on 2012 R2 is still very bad and lacks basic features
like disabling external recursion. This should change on Server 2016 but I will
FCA US LLC
>
> 1075 W Entrance Dr,
>
> Auburn Hills, MI 48326
>
> USA
>
>
>
> Telephone: +1 (248) 838-6601
> Mobile: +1 (810) 397-0103
>
> Email: kevin.da...@fcagroup.com
>
>
>
> *From:* Chris Buxton [mailto:cli...@buxtonfamily.us]
> *Sent:* Thu
Hills, MI 48326
> USA
>
> Telephone: +1 (248) 838-6601
> Mobile: +1 (810) 397-0103
> Email: kevin.da...@fcagroup.com
>
> From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Jeff
> Sadowski
> Sent: Wednesday, July 27, 2016 3:00 PM
> To: bind-users@lists.is
, July 28, 2016 12:52 PM
To: Darcy Kevin (FCA)
Cc: bind-users@lists.isc.org
Subject: Re: Multiple AD domains
The OP's question was about setting up BIND, not MS DNS, related to using
Samba, not Windows, as the domain controller.
Regards,
Chris
Sent from my iPhone
On Jul 27, 2016, at 12:36 PM,
A Information Security Projects
>
> FCA US LLC
> 1075 W Entrance Dr,
> Auburn Hills, MI 48326
> USA
>
> Telephone: +1 (248) 838-6601
> Mobile: +1 (810) 397-0103
> Email: kevin.da...@fcagroup.com
>
> From: bind-users [mailto:bind-users-boun...@lists.isc.org] On
ers@lists.isc.org<mailto:bind-users@lists.isc.org>
Subject: Re: Multiple AD domains
should I setup 192.168.1.1 as slaves to these two domains would that fix it?
On Wed, Jul 27, 2016 at 12:56 PM, Jeff Sadowski
mailto:jeff.sadow...@gmail.com>> wrote:
On the samba mailing list they described se
: Multiple AD domains
should I setup 192.168.1.1 as slaves to these two domains would that fix it?
On Wed, Jul 27, 2016 at 12:56 PM, Jeff Sadowski
mailto:jeff.sadow...@gmail.com>> wrote:
On the samba mailing list they described setting up the DC as the NS and
forward to another machine for more
I'm going to try slaves like so
If I setup slave zones like so on 192.168.1.1
zone "domainA" IN { type slave; masters { 192.168.2.1; }; file
"db.domainA"; };
zone "domainB" IN { type slave; masters { 192.168.3.1; }; file
"db.domainB"; };
and in 192.168.2.1 and 192.168.3.1
in options
notify yes;
I'm going to try slaves like so
If I setup slave zones like so on 192.168.1.1
zone "domainA" IN { type slave; masters { 192.168.2.1; }; file
"db.domainA"; };
zone "domainB" IN { type slave; masters { 192.168.3.1; }; file
"db.domainB"; };
and in 192.168.2.1 and 192.168.3.1
in options
notify yes;
should I setup 192.168.1.1 as slaves to these two domains would that fix it?
On Wed, Jul 27, 2016 at 12:56 PM, Jeff Sadowski
wrote:
> On the samba mailing list they described setting up the DC as the NS and
> forward to another machine for more rules.
> This will work fine for one domain. Now le
10 matches
Mail list logo
