search for: thisismycompany

I'm setting up a bind server as well as a samba domain on a machine (timcserv03). I initially set the local domain up in bind as thisismycompany.local (already owning the name thisismycompany.com), however I started to see that there could be issues with using .local, so wanted to go in a safer direction. It seems the best logical internal domain name would be local.thisismycompany.com. Note that I'm using the example of "thisismyc...

On Thu, Jan 22, 2015 at 4:29 AM, Peter Serbe <peter at serbe.ch> wrote: > If the domain is set up as > [global] > workgroup = LOCAL > realm = local.thisismycompany.com > then the domain users would log in as local\flast. > I am not sure, whether LOCAL makes up a good domain name... Thanks for adding clarity Peter. I'm having trouble framing my questions so maybe I might be able to better explain precisely what I'm looking for here: 1) Assuming...

zone "local.thisismycompany.com" { type slave; masters { *your DCs go here* }; file "/etc/bind/namedb/bak.local.thisismycompany.com"; forwarders{}; }; If you are setting up bind on the DC like that, you have a problem, you are not using DLZ. Rowland

if this is in smb.conf >[global] > workgroup = LOCAL > realm = local.thisismycompany.com then you have a problem. realm needs to be in CAPS Louis >-----Oorspronkelijk bericht----- >Van: peter at serbe.ch [mailto:samba-bounces at lists.samba.org] >Namens Peter Serbe >Verzonden: donderdag 22 januari 2015 10:29 >Aan: samba at lists.samba.org; jeff at henze.us >...

...k bericht----- >Van: rowlandpenny at googlemail.com >[mailto:samba-bounces at lists.samba.org] Namens Rowland Penny >Verzonden: donderdag 22 januari 2015 11:10 >Aan: samba at lists.samba.org >Onderwerp: Re: [Samba] dns/ad domain provisioning and naming > > >zone "local.thisismycompany.com" { > type slave; > masters { *your DCs go here* }; > file "/etc/bind/namedb/bak.local.thisismycompany.com"; > forwarders{}; >}; > > >If you are setting up bind on the DC like that, you have a >problem, you are not using...

...DNS information from an external forwarder (as 8.8.8.8 from Google) and the internal information from *your DCs go here*. Then the line "forwarders{};" does inhibit, that internal requested are directed to the public DNS, which might resolve these to Your public servers, which serve thisismycompany.com. I use this setup at home, where the DC is a slow Raspberry Pi. On the much faster file (a.k.a. member) server I operate the secondary DNS server with that snippet below. This may or my not be relevant to the OP... But at least I wanted to clarify the confusion. Best regards Peter R...

...m an external forwarder (as 8.8.8.8 from Google) and > the internal information from *your DCs go here*. > Then the line "forwarders{};" does inhibit, that internal > requested are directed to the public DNS, which might > resolve these to Your public servers, which serve > thisismycompany.com. > > I use this setup at home, where the DC is a slow Raspberry > Pi. On the much faster file (a.k.a. member) server I > operate the secondary DNS server with that snippet > below. > > This may or my not be relevant to the OP... > But at least I wanted to clarify the con...