File scan of DFS(SMB) - connection refused

1 Problem:
2 Symptoms
3 Root cause:
4 Solution:
5 Verification:

Problem:

Scanning of DFS/SMB is not working. Referred nodes cannot be expanded in connection wizard and scan of those is failing.

Symptoms

scanned share is DFS enabled

Subfolders/shares which are referring to another dfs nodes cannot be expanded in connection wizard
Scan of referred subfolder/share won’t find anything and error message logged in connector-generic is matching following:

Root cause:

Parent DFS server is referring to other nodes via hostnames which is not resolvable by connector’s pod.

Confirmation can be done via cli of host os - jiridfs1 is not resolvable directly

ubuntu@ip-10-30-4-52:~$ nslookup jiridfs1
Server:		10.30.4.82
Address:	10.30.4.82#53

** server can't find jiridfs1: SERVFAIL

However it can be resolved via fqdn:

ubuntu@ip-10-30-4-52:~$ nslookup jiridfs1.jiris-ad.local
Server:		10.30.4.82
Address:	10.30.4.82#53

Name:	jiridfs1.jiris-ad.local
Address: 10.30.4.35

Solution:

Add dns suffix to host os dns resolver via search directive iin /etc/resolv.conf and propagate it to connector’s pod:

ubuntu@ip-10-30-4-52:~$ sudo vim /etc/resolv.conf
search jiris-ad.local
nameserver 10.30.4.82

propagate it to coredns and connector:

Verification:

Execute new scan and confirm results and that there are no errors in logs:

Further verification of applied dns suffix can be done by checking connector-generic and it’s /etc/resolv.conf:

GV-KnowledgeBase