search for: devdc2

In addition with Rowlands comment. I suggest you try /etc/hosts add only 127.0.0.1 localhost Now type Hostname -f Hostname -s Hostname -d Hostname -I Are these all correct? > No, Edit resolv.conf domain samba.ifa.net search samba.ifa.net ifa.net nameserver 127.0.0.1 What happens now if you try the above command. Correct? Yes => correct your hosts and resolv.conf No || \/

...DNS update - NT_STATUS_UNSUCCESSFUL > > Now to try and find the cause and fix it. > > Rowland > OK, I think I have sorted this, I added some lines to samba_dnsupdate to print out why it didn't work and got this: Could not obtain Kerberos ticket for DNS/devdc1.example.com as DEVDC2$ response to GSS-TSIG query was unsuccessful .... response to GSS-TSIG query was unsuccessful Failed update of 24 entries So, I thought, no SOA records for DEVDC2 Added them: samba-tool dns add 127.0.0.1 example.com devdc2 A 192.168.0.251 -Uadministrator samba-tool dns add 127.0.0.1 example.com...

...d then samba, this should run samba_dnsupdate and add all the missing records. You can check this with: host -t SRV _ldap._tcp.example.com. You should get a result similar to this: _ldap._tcp.example.com has SRV record 0 100 389 devdc1.example.com. _ldap._tcp.example.com has SRV record 0 100 389 devdc2.example.com. edit /etc/resolv.conf on both DCs to use the other as a nameserver and then itself: DC1: search example.com nameserver 192.168.0.251 nameserver 127.0.0.1 DC2: search example.com nameserver 192.168.0.250 nameserver 127.0.0.1 Finally, restart samba on both DCs Rowland

...nsupdate and add all > the missing records. You can check this with: > > host -t SRV _ldap._tcp.example.com. > > You should get a result similar to this: > > _ldap._tcp.example.com has SRV record 0 100 389 devdc1.example.com. > _ldap._tcp.example.com has SRV record 0 100 389 devdc2.example.com. > > edit /etc/resolv.conf on both DCs to use the other as a nameserver and > then itself: > > DC1: > > search example.com > nameserver 192.168.0.251 > nameserver 127.0.0.1 > > DC2: > > search example.com > nameserver 192.168.0.250 > nameserv...