search for: bind9dlz

Hi everyone. I have a Linux nsupdate client sending dns update requests via sssd. Just gone from 4.1.2 to 4.1.3. I've done this: http://linuxcostablanca.blogspot.com.es/2013/09/samba4-bind9dlz-stale-dns-records-with.html After which the forward zone update is working fine: 2014-01-10T12:32:35.376142+01:00 hh16 named[4963]: samba_dlz: starting transaction on zone hh3.site 2014-01-10T12:32:35.382352+01:00 hh16 named[4963]: samba_dlz: allowing update of signer=CATRAL\$\@HH3.SITE name=catr...

Samba 4.1.1 using BIND_DLZ (bind-9.9.1-0.1.P2) on CentOS 6.5 x86_64. I have two domain controllers, dc-1 and dc-2, which each have three network interfaces. Selinux is in permissive mode, and iptables is off. One interface on each dc is to be shut down. So, on dc-1, I do: # nsupdate -g update delete europa.icse.cornell.edu A 192.168.3.250 update delete europa.icse.cornell.edu A 192.168.3.251

I'm getting fed up with the whole DNS scenario with Samba4. I'm literally about to go insane. I've spent about 60 hours in the last two weeks and I can't seem to figure out a solution that meets my requirements. So what are my requirements? * A Samba4 AD domain. * A DHCP server for approx 100 windows clients/devices * A DNS server whose forward and reverse zones get updated when

Hi Rowland, Thank you. Yes to the first point. We are using Bind9 but to continue using it is not necessarily set in stone. If using Samba Internal DNS makes more sense then we can do that too. The question is do we need to do dns-upgrade and use Internal DNS, pre-migration? Then use internal dns during the classic migration? Also, I assume the bind9 service will have to stopped if infact we