#DNS response time

1 messages · Page 1 of 1 (latest)

paper summit
#

We are observing DNS response times of ~3000ms, occasionally reaching ~4000ms for SVM "xyz". Users are unable to access the file shares via IP, though it works with the FQDN. However, intermittently, neither method works. This issue is specific to a single SVM "xyz" that is on a different domain, and we are not seeing similar issues with any other SVMs on same filer.

Also, when I do "cifs check -vserver xyz", it shows status as "down" and status details "Unable to contact DNS"

NetApp Model - AFF-A300

Could you please advise on what might be causing this issue?

unborn beacon
#

check the event logs specific to the svm?
check the SVM domain password and dns config?
ping the dns server from the SVM lif
enable debug logging if need be

#

cifs domain discovered-servers shows -vserver XXX
cifs domain discovered-servers discovery mode show -vserver XXX
vserver services dns show
network ping -vserver XXX -lif SVM_mgmt_lif -destination DNS_Server
event log show -time >5m (5min history)
event log show -message-name cifs -node XXX
event log show -message-name dns -node XXX
debug log show -incl-files secd -timestamp >5m
ns-switch show -vserver XXX
getxxbyyy gethostbyaddr -ipaddress DNS_IP -vserver XXX -node XXX
dns hosts show -vserver XXX

etc

smoky verge
#

I'd first be doing the ping of the DNS Servers from the SVM's LIFs, as mentioned above, and also checking the routes on the SVM. Ensure the route that will get the SVM to the DNS Server IPs is using the correct gateway.

You mention they can reach it via FQDN but not IP. I assume the simple check has been done, does the FQDN resolve to the same IP?

Also, access direct to the IP will not work on a CIFS server if you've got the cifs security settings configured to only allow Kerberos. KRB requires the FQDN is used from the client.