Resolve Verisign Secure Domain CSR Error "Due to new CA/Browser Forum changes, Internal Server names and private IP addresses will not be available for use after July 15,2016..."

One of the Prerequisites for setting up a Custom Secure Domain is to generate a Certificate Signing Request (CSR)
 

To generate the CSR:

1. Open a command prompt. Navigate to Start > Accessories > Command Prompt, or type
CMD in the Run window.
2. Type C: and then press Enter to change the directory.
3. Type openssl and then press Enter.
4. Type the following command:
req –new –key <secure.domainnamekey>.key –out <secure.domainnamecsr>.csr
 

Note: This command will prompt the user to enter the following X.509 attributes for the certificate

1. Ensure that the Common Name that will be used is the host or domain name such as secure.mydomain.com or store.mydomain.com.
2. Only use certificates for the Common Name specified during enrollment.

For example, a certificate for the domain checkout.mydomain.com will generate a warning if the site is actually named www.domain.com or store.domain.com.

The below error message will show in Verisign website once you validate the CSR.
Verisign will not allow you to submit the CSR.

Due to new CA/Browser Forum changes, Internal Server names and private IP addresses will not be available for ise after July 15,2016. We recommend that you enter a qualified domain name to continue.