Installer could not verify if A record present / network unhealthy

Hi,

during installation of ExchSvr2013 CU7 I'd received a warning, that install could not determine if there is an A record for the server in the DNS. I know, setup could also abort the installation with an error, saying that there *IS NO* A record in the DNS, however it was only a warning only and installation was possible. After the installation, get-healthreport lists everything healthy except of network.

Needles to say that there is an A record (as well as PTR record) and name resolution is working properly. So I'm wondering why setup could not doublecheck this on its own and, if this is also the reason why network is reported unhealthy.

The server is currently AD, DNS, DHCP. I know, it's not recommended to install ExchSvr on AD server, but due to migration from 2003SBS, I need to do so temporarily. Could this be the reason why Setup is unable to query DNS by itself?

Best regards
Holger


  • Edited by Holger Keil Sunday, February 01, 2015 2:49 AM
February 1st, 2015 5:45am
To be honest, disabling/removing IPv6 could not be the solution, at least since microsoft no longer recommends to do so.
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2015 5:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics