DNS paerially failed after release upgrade from 3.0 to 3.2

ifabrizio · ‎08-07-2023

Hi to All,

After the upgrade from 3.0 patch7 to 3.2 Patch2, the Health Checks about DNS, fail.

Before the upgrade it works.

Follow the error message, I have removed the DNS ip address and the Ise node names:

But if I try from ISE nodes CLI to do the nslookup about the ISE node names, using the same DNS servers, it works...

Could you help me pls?

Bye,

JF.

ahollifield · ‎08-08-2023

Do both nodes point to the same DNS servers? Looks like your reverse (PTR) DNS lookups are successful but your A records are not.

ifabrizio · ‎08-09-2023

Hi Ahollifield,

Thank you for your reply.

Yes I confirm that both nodes point to the same DNS servers.

The Ise is still working well, but I got this error in the Health Checks, it was started after the upgrade from 3.0 to 3.2.

Bye,

JF