Yes, that's the configuration I had when I installed it on my Raspberry Pi.

On my Debian 9 VM, here are the different files:

/etc/samba/smb.conf:

# Global parameters
[global]
dns forwarder = 192.168.1.1
netbios name = SRVADS
realm = DOHAKOR.LAN
server role = active directory ...

Yes, indeed, with the dig command. I don't have any problems with this command.

Here's what I get:

root@srvads:~# netstat -tapn | grep 53
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 772/samba: task[dns
tcp 0 0 0.0.0.0:49153 0.0.0.0:* LISTEN 757/samba: task[dce
tcp6 0 0 :::53 :::* LISTEN 772 ...

Hello,

I searched this weekend and couldn't find a way to fix this DNS problem.

Furthermore, when I ran the commands from the Verifying DNS section of the Samba wiki, I got this:

root@srvads:~# host -t SRV _ldap._tcp.dohakor.lan
Host _ldap._tcp.dohakor.lan not found: 3(NXDOMAIN)
root@srvads ...

I tried your command and here's the result:

root@srvads:~# samba_dnsupdate --use-samba-tool
Failed to get Kerberos credentials, falling back to samba-tool: kinit for SRVADS$@DOHAKOR.LAN failed (Cannot contact any KDC for requested realm)

ERROR(runtime): uncaught exception - (9711, 'WERR_DNS ...

I finally managed to run the kinit Administrator and klist commands!!!

I looked at this post ===> https://serverfault.com/questions/166768/kinit-wont-connect-to-a-domain-server-realm-not-local-to-kdc-while-getting-in

So I modified my /etc/krb5.conf file to change from:

[libdefaults ...

I tried and still nothing:

root@srvads:~# kinit administrator
kinit: Cannot contact any KDC for realm 'DOHAKOR.LAN' while getting initial credentials
root@srvads:~# klist
klist: No credentials cache found (filename: /tmp/krb5cc_0)

And after adding your modification, I do have the part...

So, generally for my tests, I always prefer to have the same type of installation:

- Raspbian: lite version with only SSH enabled
- Debian: "small installation image" version with the bare minimum ("SSH" and "standard system utilities")

I'm going to add the lines to...

Hello,

thank you for your reply :).

That's exactly what I did on my VMs; I do have a static IP address:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The ...

After attempting an installation under Debian 9 (VM), I am still encountering the same error.

Initially, I performed a small installation on a VM.

I'm still having the problem with the `kinit administrator` command:

`kinit: Cannot find KDC for realm "DOHAKOR.LAN" while getting initial credentials`.

However, I'm getting better results for the DNS test:

`dig ...`