I am using samba4 on debian squeeze virtualized on proxmox. git snapshot 968da5f. today morning. I compiled and installed as usual. Though this is my first time using the internal DNS server. The internal DNS server is not doing automatic updates. And this is the message I get in log.samba: /usr/local/samba/sbin/samba_dnsupdate: RuntimeError: kinit for AD$@EPEPM.CUPET.CU failed (Client not found in Kerberos database) [2012/09/26 13:35:24, 0] ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) Any idea of what is going wrong? Cheers, Felix.
> > > I am using samba4 on debian squeeze virtualized on proxmox. > > git snapshot 968da5f. today morning. > > I compiled and installed as usual. > > Though this is my first time using the internal DNS server. > > The internal DNS server is not doing automatic updates. And this is the > message I get in log.samba: > > /usr/local/samba/sbin/samba_dnsupdate: RuntimeError: kinit for > AD$@EPEPM.CUPET.CU failed (Client not found in Kerberos database) > [2012/09/26 13:35:24, 0] > ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) > > > Any idea of what is going wrong? >It seems that the internal DNS server doesnt like the original administrator user. When I created a new user with administrative rights everything went OK. Cheers, Felix.
>> >> >> I am using samba4 on debian squeeze virtualized on proxmox. >> >> git snapshot 968da5f. today morning. >> >> I compiled and installed as usual. >> >> Though this is my first time using the internal DNS server. >> >> The internal DNS server is not doing automatic updates. And this is the >> message I get in log.samba: >> >> /usr/local/samba/sbin/samba_dnsupdate: RuntimeError: kinit for >> AD$@EPEPM.CUPET.CU failed (Client not found in Kerberos database) >> [2012/09/26 13:35:24, 0] >> ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) >> >> >> Any idea of what is going wrong? >> > > It seems that the internal DNS server doesnt like the original > administrator user. When I created a new user with administrative rights > everything went OK. >in fact it was a problem in resolv.conf. it was pointing to another dns server instead of itself. my mistake. it ocurred because i changed resolv.conf to the right options but as i am virtualizing with proxmox i forgot to change dns setting in the container so it took the previous value at restart.