Hi, Not sure exactly how I would word the subject line so appologies in advanced. We are trying to accomplish the following scenario: Location 1: PDC: fs01.loc1.example.com IP: 10.0.0.1 Location 2: SDC: fs01.loc2.example.com IP: 10.0.1.1 Clearly when we join the SDC to the PDC there is a naming conflict. The end result would be to have clients at each site resolve the fs01 name to the local site while retaining the credential synchronization across the two locations. We were initially using the BIND9_DLZ dns backend however we were having difficulties in getting the dynamic updates workign from windows clients. Is the above senario possible to accomplish with a SAMBA_INTERNAL dns backend? If so could you point me in the correct direction. As a workaround we have renamed the DCs and added static entries in the hosts files and pushing out the DNS suffixes to windows client machines for the respective locations. Hoping we can integrate this into the internal DNS somehow though. Kind regards, John Crombie
On Wed, 16 Nov 2016 15:43:36 +1100 (EST) John Crombie via samba <samba at lists.samba.org> wrote:> > Hi, > > Not sure exactly how I would word the subject line so appologies in > advanced. > > We are trying to accomplish the following scenario: > > Location 1: > PDC: fs01.loc1.example.com > IP: 10.0.0.1 > > Location 2: > SDC: fs01.loc2.example.com > IP: 10.0.1.1 > > Clearly when we join the SDC to the PDC there is a naming conflict. > The end result would be to have clients at each site resolve the fs01 > name to the local site while retaining the credential synchronization > across the two locations. We were initially using the BIND9_DLZ dns > backend however we were having difficulties in getting the dynamic > updates workign from windows clients. Is the above senario possible > to accomplish with a SAMBA_INTERNAL dns backend? If so could you > point me in the correct direction. > > As a workaround we have renamed the DCs and added static entries in > the hosts files and pushing out the DNS suffixes to windows client > machines for the respective locations. Hoping we can integrate this > into the internal DNS somehow though. > > > > Kind regards, > John CrombieWhen you say 'PDC', do you really mean 'an AD DC' and when you say 'SDC', do you really mean 'another AD DC' ?? If so, this isn't going to work, not only because you are trying to use the same server name, you are also using different dns names. I think you need to investigate 'SITES' Rowland
Am 16.11.2016 um 05:43 schrieb John Crombie via samba:> > Hi, > > Not sure exactly how I would word the subject line so appologies in advanced. > > We are trying to accomplish the following scenario: > > Location 1: > PDC: fs01.loc1.example.com > IP: 10.0.0.1 > > Location 2: > SDC: fs01.loc2.example.com > IP: 10.0.1.1 >The Hostname is the NetBIOS-Name and it's an Address, so it must be unique. So fs1 can only be used once.> Clearly when we join the SDC to the PDC there is a naming conflict. The end result would be to have clients at each site resolve the fs01 name to the local site while retaining the credential synchronization across the two locations. We were initially using the BIND9_DLZ dns backend however we were having difficulties in getting the dynamic updates workign from windows clients. Is the above senario possible to accomplish with a SAMBA_INTERNAL dns backend? If so could you point me in the correct direction. >To manage this you should uses sites and subnet-setting. So create sites and subnet and everythin will work> As a workaround we have renamed the DCs and added static entries in the hosts files and pushing out the DNS suffixes to windows client machines for the respective locations. Hoping we can integrate this into the internal DNS somehow though. > > > > Kind regards, > John Crombie >-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20161116/224749c7/signature.sig>