search for: bywater

Displaying 4 results from an estimated 4 matches for "bywater".

2017 Jun 07
4
Samba4 DC with Secondary Questions
...trator" --dns-backend=BIND9_DLZ --server bagend.shire.middleearth does this type of join command automatically create this Seconday as kerberos slave? The reason I want a slave is so that I have some redundancy in the network, where Primary (bagend) lives on one VM hypervisor, and Secondary (bywater) lives on a different VM Hypervisor. If this does not automatically create Secondary/bywater as a kerberos slave, are there any 'gotchya's I need to watch our for when I manually add this secondary as a kerberos slave? Will doing so automatically update the domain? I wondered if during sa...
2017 Jun 07
0
Samba4 DC with Secondary Questions
...t; > does this type of join command automatically create this Seconday as > kerberos slave? No, as I said above, all DCs are equal. > The reason I want a slave is so that I have some > redundancy in the network, where Primary (bagend) lives on one VM > hypervisor, and Secondary (bywater) lives on a different VM > Hypervisor. If this does not automatically create Secondary/bywater > as a kerberos slave, are there any 'gotchya's I need to watch our for > when I manually add this secondary as a kerberos slave? Will doing > so automatically update the domain? All...
2017 Jun 07
1
Samba4 DC with Secondary Questions
...command automatically create this Seconday as > > kerberos slave? > > No, as I said above, all DCs are equal. > > > The reason I want a slave is so that I have some > > redundancy in the network, where Primary (bagend) lives on one VM > > hypervisor, and Secondary (bywater) lives on a different VM > > Hypervisor. If this does not automatically create Secondary/bywater > > as a kerberos slave, are there any 'gotchya's I need to watch our for > > when I manually add this secondary as a kerberos slave? Will doing > > so automatically upd...
2012 Feb 01
2
Yes another "I can't open port 53 for Bind DNS"
Hi, It's just past 3am and for the past 6 hours I've been configuring a secondary name server to replace one that just crashed. My problem appears to be that port 53 is not open for some reason on my server even though I have this: [root at tribe etc]# netstat -an | grep ":53 " tcp 0 0 205.211.154.3:53 0.0.0.0:* LISTEN tcp