[Samba] parse_dfs_path_strict: Hostname XXX is not ours.

[Michael Tokarev]

Hi!

I noticed massive logging on one of our servers, like the above.

[2026/09/15 09:06:08.354265,  0, pid=2251327] source3/smbd/msdfs.c:120(parse_dfs_path_strict)
   parse_dfs_path_strict: Hostname ekis-files is not ours.
[2026/09/15 09:06:08.490609,  0, pid=2251327] source3/smbd/msdfs.c:120(parse_dfs_path_strict)
   parse_dfs_path_strict: Hostname EKIS-FILES.RGS.INT is not ours.
[2026/09/15 09:06:19.610801,  0, pid=2251327] source3/smbd/msdfs.c:120(parse_dfs_path_strict)
   parse_dfs_path_strict: Hostname ekis-files is not ours.

etc etc.

It is not this server's name indeed.

There are 2 servers, ekis-files and mars (this one where this message is from).
For some share, there's a dfs-link FROM ekis-files to mars:

[files]
msdfs proxy = \mars.rgs.int\files


And on mars (this server), there's no DFS configuration at all.

So a client connects to \\ekis-files\files, and gets redirected to
\\mars\files instead, which contains actual files.

How it's possible to get into this codepath on \\mars which is a
*target* of the DFS link, with a name of the *source* of that link?
The DNS points to the correct hosts.

I'd love to debug this further but it's a large production system.
Where I'm trying to debug another issue :)

Thanks,

/mjt