Hi,
thanks for the pointer, I missed that discussion.
I'm seeing the same error. We do have reverse DNS records for our Storage systems IPs, and running firmware 8.6.0.7, so seems we have to wait for a newer PTF :(
Best regards,
Alexander
------------------------------
Alexander Reichle-Schmehl
------------------------------
Original Message:
Sent: Thu May 15, 2025 05:22 AM
From: Nezih Boyacioglu
Subject: Handling of rebooting nameservers
Hi Alexander,
If you get "Could not connect to DNS server" notifications you can check https://community.ibm.com/community/user/discussion/error-1585-could-not-connect-to-dns-server-since-upgrading-to-8604
------------------------------
Nezih Boyacioglu
Original Message:
Sent: Thu May 15, 2025 04:13 AM
From: Alexander Reichle-Schmehl
Subject: Handling of rebooting nameservers
Hi!
We use various kinds FlashSystem 5xxx and San Volume Controller in several of our subsidiaries. However, we are facing an annoyance when configuring them to use name servers.
In our environment we have use internal DNS servers. The service is hosted on the AD servers by the Windows server colleagues, who periodically have to reboot them when installing updates.
(Nearly) every time they do so, our FlashSystems and SVC notice that and raise an error.
It also seems that we have to use DNS to be able to use an internal proxy - at least in firmware 8.7.0.x I can't specify the proxy by IP.
We use several name servers, and our colleagues make sure to not reboot them at the same time. So technically, we don't have a problem, but are "spammed" by the notifications mails (which are also send to our ticket system, so we have clean them up there).
Is there any way we can solve this annoyances? Can somehow downgrade this specific error to a plain information event? Or increase the threshold for it to two name servers unreachable?
Best regards,
Alexander