[Solve]The fully qualified domain name for node could not be found.

On my last blog, I had a talk about DAG (Database Availability Group) on Exchange 2016. Fortunately, I had smooth configuration but luck doesn’t go every day like that. Here is one of the issue you might face during the configuration of DAG and also I have posted resolution on it.

Configuring Exchange Certificate

Another important part of the exchange server is to configure the certificate. Certificate makes the web-based mail access secure as well authenticated and this part is quite recommended on the enterprise level, if we check from the Exchange 2013 all the console is browser based. To configure the certificate on the Exchange server it requires a public certificate with minimum One (1) Subject Alternative Name (SAN) to access mail through public (Internet). Number of SAN depends upon the no. of Domain we use.

Normally after the installation of the Exchange server, if we try to access the browser we see the error as of the below screenshot that has been taken. To avoid this screen, we need to have a public/private certificate. If we are using Private certificate that, this will not work if we try to access email on browser based through internet. But if we do have a pubic certificate, it will allow us secure connection for both public and private network.