Hi Michael,
On Tue, Feb 21, 2012 at 11:57 PM, Michael Wood esiot...@gmail.com wrote:
Since I provisioned samba4 before the DLZ option was available I have
stuck with BIND9_FLATFILE for now.
I have pushed upgradedns script to upgrade DNS provisioning from BIND9_FLATFILE
backend to BIND9_DLZ
HI Michael,
On Wed, Feb 22, 2012 at 7:06 PM, Michael Wood esiot...@gmail.com wrote:
Hi
On 22 February 2012 01:46, jdf...@cox.net wrote:
The default DNS backend has changed to BIND9_DLZ. This means the DNS
records are stored in Samba4's AD tree instead of in a normal zone
file.
[...]
If
Hi Jeremy,
On Thu, Feb 23, 2012 at 4:01 AM, jdf...@cox.net wrote:
Hello All,
Thank you for your help that you have provided so far regarding my issue. I
have cleared out this email to reduce the confusion of my current issue. Here
is a recap of my issue and the logs you requested below.
Hi Jeremy,
On Thu, Feb 23, 2012 at 3:29 PM, Jeremy Davis jdavis4...@gmail.com wrote:
Hello Amitay,
On 02/22/2012 02:34 PM, Amitay Isaacs wrote:
Hi Jeremy,
That error message needs to be fixed. :)
Looks like nsupdate command is not in the path. samba_dnsupdate
script uses nsupdate to
On Thu, Feb 23, 2012 at 4:33 PM, Jeremy Davisjdavis4...@gmail.com wrote:
I forgot to mention that nsupdate command should also include -g
flag to
force
secure (kerberos) updates.
nsupdate command = /path/to/nsupdate -g
dlz_bind9 module only allows secure dynamic updates.
Amitay.
I
Hello All,
On 02/23/2012 09:31 AM, Jeremy Davis wrote:
On Thu, Feb 23, 2012 at 4:33 PM, Jeremy Davisjdavis4...@gmail.com
wrote:
I forgot to mention that nsupdate command should also include -g
flag to
force
secure (kerberos) updates.
nsupdate command = /path/to/nsupdate -g
dlz_bind9
On 22 February 2012 00:58, Amitay Isaacs ami...@gmail.com wrote:
Hi Michael,
On Tue, Feb 21, 2012 at 11:57 PM, Michael Wood esiot...@gmail.com wrote:
Since I provisioned samba4 before the DLZ option was available I have
stuck with BIND9_FLATFILE for now.
I have pushed upgradedns script to
Hi
On 22 February 2012 01:46, jdf...@cox.net wrote:
The default DNS backend has changed to BIND9_DLZ. This means the DNS
records are stored in Samba4's AD tree instead of in a normal zone
file.
[...]
If you're just starting out, you might want to try the DLZ backend.
Thank you for your
On 22 February 2012 03:16, jdf...@cox.net wrote:
One note I would like to add. I am now using Bind 9.8.1 compiled from source.
It seems to load the DLZ driver just fine. The issue I am having is that
samba4 is trying to update DNS and can't. When I add a new server to the
domain DNS can't
Hi Amitay
I think you may be getting mixed up between my issues with upgrading
and the original poster's (Jeremy/jdfire) issue with a new provision
:)
The messages from the logs are all from Jeremy. It's a new provision,
so there's no migration unless I'm missing something.
My issues with
Hello All,
Thank you for your help that you have provided so far regarding my issue. I
have cleared out this email to reduce the confusion of my current issue. Here
is a recap of my issue and the logs you requested below.
Currently, I have resolved the DNSSEC issue that I was seeing in my
Hello Amitay,
On 02/22/2012 02:34 PM, Amitay Isaacs wrote:
Hi Jeremy,
That error message needs to be fixed. :)
Looks like nsupdate command is not in the path. samba_dnsupdate
script uses nsupdate to dynamically update DNS entries.
Try adding nsupdate command = /path/to/nsupdate in smb.conf.
Hello Amitay,
On 02/22/2012 10:07 PM, Amitay Isaacs wrote:
Hi Jeremy,
On Thu, Feb 23, 2012 at 3:29 PM, Jeremy Davisjdavis4...@gmail.com wrote:
Hello Amitay,
On 02/22/2012 02:34 PM, Amitay Isaacs wrote:
Hi Jeremy,
That error message needs to be fixed. :)
Looks like nsupdate command is
On 02/23/2012 06:33 AM, Jeremy Davis wrote:
Hello Amitay,
On 02/22/2012 10:07 PM, Amitay Isaacs wrote:
Hi Jeremy,
On Thu, Feb 23, 2012 at 3:29 PM, Jeremy Davisjdavis4...@gmail.com
wrote:
Hello Amitay,
On 02/22/2012 02:34 PM, Amitay Isaacs wrote:
Hi Jeremy,
That error message needs to
Hi
On 21 February 2012 13:26, JDFire jdf...@cox.net wrote:
Hello List,
I am trying to compile and install Samba 4 using the wiki guide on Centos
6.2. I am currently using the current source from git. It seems that the zone
file used for Bind is not configured and not installed in the
On 02/21/2012 12:26 PM, JDFire wrote:
Hello List,
I am trying to compile and install Samba 4 using the wiki guide on Centos 6.2.
I am currently using the current source from git. It seems that the zone file
used for Bind is not configured and not installed in the private directory.
Is there
The default DNS backend has changed to BIND9_DLZ. This means the DNS
records are stored in Samba4's AD tree instead of in a normal zone
file.
I've not tried the above, so am not sure exactly how to set it up.
There are some posts about it in the samba-technical mailing list
archives,
On 02/22/2012 12:46 AM, jdf...@cox.net wrote:
The default DNS backend has changed to BIND9_DLZ. This means the DNS
records are stored in Samba4's AD tree instead of in a normal zone
file.
I've not tried the above, so am not sure exactly how to set it up.
There are some posts about it in the
steve st...@steve-ss.com wrote:
On 02/22/2012 12:46 AM, jdf...@cox.net wrote:
The default DNS backend has changed to BIND9_DLZ. This means the DNS
records are stored in Samba4's AD tree instead of in a normal zone
file.
I've not tried the above, so am not sure exactly how to set
--
Thank you for your help! I was able to get a new Bind version to somewhat
work. I was able to join an XP machine to the domain but DNS seems to not
be updating correctly. Below you will find the logs that I am seeing.
/var/log/messages:
Feb 21 16:39:39 davis
20 matches
Mail list logo
