On 8/17/18 11:58 AM, Rowland Penny via samba wrote:> That's a problem to start with, you really are better off with multiple > DC's. I personally would use at least three in your case, one main DC > and another DC in each site. This would ensure that you would have > some fall back if a DC died.Let's for a moment assume: _ this is a test setup; _ my network is very small (read 5-10 clients); _ I cannot afford 3 DCs; _ I really want to use internal DNS (unless a showstopper comes up); _ I know I'm going with a subobtimal setup; _ I won't come and whine here if the overall thing is slow and/or not so resilient.>> In any case, do you have a pointer to some documentation I can use >> (especially WRT to DNS)? > > Yes, it is called the Samba wiki :-) > > https://wiki.samba.org/index.php/Main_PageThanks. I think I've read almost it all several times in the past. However, as I said, checking it once again, I was not able to find the information I'm looking for. Could you please point me to the pages I should be looking into in order to configure an AD DC DNS for use on two subnets? If I added a second interface to the DC right now, I guess it would answer equally on both interfaces. However, I suppose possibly: _ client 192.168.0.x should be told dc.mydom.it=192.168.0.z, while _ client 192.168.1.y should be told dc.mydom.it=192.168.1.z. If this assumption is right, I don't have an idea on how to achieve this with internal DNS. Perhaps this assumption is wrong, and the distinction should be made earlier when the SRV records are queried? Again, how? I read in MS documentation about "IP Addresses mapping to Site Names", but again, you said sites are not strictly required, so I'm trying to figure out how this would work without them. bye & Thanks av.
If you want o do it with one DC (not recommended for redundancy), then carry on. Setup the DC as per normal. Ensure that it is listening on both interfaces, and have your clients pointing to it for its DNS server. Assuming the DC is at 192.168.0.2 and 192.168.1.2, both on a /24 subnet, you should have two DHCP servers, and you should be able to hand out a specific DNS server to clients. Then, it will Just Work (TM). As long as that IP address is accessible. If you want to expand it, or have room to grow, then you'd get multiple DCs (remember, it can run as a VM too on cheap hardware), then you can start using Sites and Subnets, which will assign certain subnets to certain DCs (by default). On Fri, Aug 17, 2018 at 8:28 AM Andrea Venturoli via samba < samba at lists.samba.org> wrote:> On 8/17/18 11:58 AM, Rowland Penny via samba wrote: > > > That's a problem to start with, you really are better off with multiple > > DC's. I personally would use at least three in your case, one main DC > > and another DC in each site. This would ensure that you would have > > some fall back if a DC died. > > Let's for a moment assume: > _ this is a test setup; > _ my network is very small (read 5-10 clients); > _ I cannot afford 3 DCs; > _ I really want to use internal DNS (unless a showstopper comes up); > _ I know I'm going with a subobtimal setup; > _ I won't come and whine here if the overall thing is slow and/or not so > resilient. > > > > > > >> In any case, do you have a pointer to some documentation I can use > >> (especially WRT to DNS)? > > > > Yes, it is called the Samba wiki :-) > > > > https://wiki.samba.org/index.php/Main_Page > > Thanks. > I think I've read almost it all several times in the past. > However, as I said, checking it once again, I was not able to find the > information I'm looking for. > Could you please point me to the pages I should be looking into in order > to configure an AD DC DNS for use on two subnets? > > > > If I added a second interface to the DC right now, I guess it would > answer equally on both interfaces. > > However, I suppose possibly: > _ client 192.168.0.x should be told dc.mydom.it=192.168.0.z, while > _ client 192.168.1.y should be told dc.mydom.it=192.168.1.z. > > If this assumption is right, I don't have an idea on how to achieve this > with internal DNS. > > Perhaps this assumption is wrong, and the distinction should be made > earlier when the SRV records are queried? > Again, how? > > > > I read in MS documentation about "IP Addresses mapping to Site Names", > but again, you said sites are not strictly required, so I'm trying to > figure out how this would work without them. > > > > bye & Thanks > av. > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
If you have a router between vlans, you just put you DC on any one of the vlans, DC should work better on one NIC. In my environment, I have 3 DCs(with single NIC) on 2 vlans(vpn connection) and 200 machines located on the other 7 vlans. Everything just works. Allen On 8/17/2018 11:57 AM, Luke Barone via samba wrote:> If you want o do it with one DC (not recommended for redundancy), then > carry on. > > Setup the DC as per normal. Ensure that it is listening on both interfaces, > and have your clients pointing to it for its DNS server. Assuming the DC is > at 192.168.0.2 and 192.168.1.2, both on a /24 subnet, you should have two > DHCP servers, and you should be able to hand out a specific DNS server to > clients. > > Then, it will Just Work (TM). As long as that IP address is accessible. If > you want to expand it, or have room to grow, then you'd get multiple DCs > (remember, it can run as a VM too on cheap hardware), then you can start > using Sites and Subnets, which will assign certain subnets to certain DCs > (by default). > > On Fri, Aug 17, 2018 at 8:28 AM Andrea Venturoli via samba < > samba at lists.samba.org> wrote: > >> On 8/17/18 11:58 AM, Rowland Penny via samba wrote: >> >>> That's a problem to start with, you really are better off with multiple >>> DC's. I personally would use at least three in your case, one main DC >>> and another DC in each site. This would ensure that you would have >>> some fall back if a DC died. >> Let's for a moment assume: >> _ this is a test setup; >> _ my network is very small (read 5-10 clients); >> _ I cannot afford 3 DCs; >> _ I really want to use internal DNS (unless a showstopper comes up); >> _ I know I'm going with a subobtimal setup; >> _ I won't come and whine here if the overall thing is slow and/or not so >> resilient. >> >> >> >> >> >>>> In any case, do you have a pointer to some documentation I can use >>>> (especially WRT to DNS)? >>> Yes, it is called the Samba wiki :-) >>> >>> https://wiki.samba.org/index.php/Main_Page >> Thanks. >> I think I've read almost it all several times in the past. >> However, as I said, checking it once again, I was not able to find the >> information I'm looking for. >> Could you please point me to the pages I should be looking into in order >> to configure an AD DC DNS for use on two subnets? >> >> >> >> If I added a second interface to the DC right now, I guess it would >> answer equally on both interfaces. >> >> However, I suppose possibly: >> _ client 192.168.0.x should be told dc.mydom.it=192.168.0.z, while >> _ client 192.168.1.y should be told dc.mydom.it=192.168.1.z. >> >> If this assumption is right, I don't have an idea on how to achieve this >> with internal DNS. >> >> Perhaps this assumption is wrong, and the distinction should be made >> earlier when the SRV records are queried? >> Again, how? >> >> >> >> I read in MS documentation about "IP Addresses mapping to Site Names", >> but again, you said sites are not strictly required, so I'm trying to >> figure out how this would work without them. >> >> >> >> bye & Thanks >> av. >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >>-- Allen Chen Network Administrator IT Harbourfront Centre 235 Queens Quay West, Toronto, ON M5J 2G8, Canada | harbourfrontcentre.com <http://www.harbourfrontcentre.com> Office: +1 416 973-7973 Cell: +1 416 556-249