I did read through that, but unfortunately I don't think it applies to us. We already have the appropriate A and PTR records created for our storage arrays. IBM support also mentioned that testing the DNS IP(s) using a reverse lookup was introduced in 8.6 and we were running 8.6.0.2 prior to the 8.6.0.4 upgrade without any alerts. Appreciate the reply, though!
------------------------------
Travis Bailey
Steelcase Inc
Grand Rapids
------------------------------
Original Message:
Sent: Fri June 14, 2024 02:21 PM
From: Thomas Greß
Subject: error 1585 (Could not connect to DNS server) since upgrading to 8.6.0.4
Hi,
I had the same issue. Here is what I did:
https://community.ibm.com/community/user/storage/discussion/warning-event-notification-could-not-connect-to-dns-server?ReturnUrl=%2fcommunity%2fuser%2fstorage%2fcommunities%2fcommunity-home%2fdigestviewer%3fcommunitykey%3d259eb30e-f20d-4433-aa35-ff2bc9bf625f
"Hi,
I found the solution to fix this problem. I researched the DNS server logs. The Flasystem is trying to get a PTR record for its IP address. Most of the answers were answered with "NXDOMAIN". But some with "SERVFAIL". When "SERVFAIL" occurred, I received the message from the storage.
Solution: Create PTR entry for the storage. Since then there has been no further notification."
------------------------------
Thomas Greß
Original Message:
Sent: Fri June 14, 2024 09:09 AM
From: Travis Bailey
Subject: error 1585 (Could not connect to DNS server) since upgrading to 8.6.0.4
We have a number of FlashSystem 7300s in production as well as a 5045 in our test environment. Everything was running 8.6.0.2 prior to our 8.6.0.4 upgrade and ever since we are getting these 1585 errors sometimes multiple times per day. Our 5045 array was the first to get upgraded and have received the errors ever since. Our 7300s were the next to get upgraded and the same thing, 1585 errors after the upgrade. I've tried multiple DNS entries and no matter what I do we continue to receive these errors. I know there were some changes in 8.6 as to how DNS is tested, but I don't understand why the issue suddenly started with such a minor upgrade and nothing changing on the DNS front. I created a case with support and they basically told us our DNS servers are the problem...even though this issue never happened prior to the 8.6.0.4 upgrade. Does anyone have any thoughts of what else I should check?
------------------------------
Travis Bailey
Steelcase Inc
Grand Rapids
------------------------------