Public CA do not allow internal names and reserved IP address any more
With November 2015 public CAs do not issue new certificates that uses internal names or reserved IP addresses in subjectAltName or in commonName. Furthermore such certificates will be revoked on October 1st, 2016.
Internal names are hostnames that do not end with an Top Level Domain ending (.com, .de, …). For example: .local, .internal. Also NetBIOS names without any domain extension are affected.
Reserved IP addresses are defined by Internet Assigned Numbers Authority (IANA). You can look reservations for IPv4 here (RFC 1918 range) and IPv6 here (RFC 4193 range).
If you are using an internal CA you are not affected. For more information about this change of public CAs click here. For more information about VMware products click here.
2 responses to “Public CA do not allow internal names and reserved IP address any more”
Leave a Reply
Veeam Vanguard
Veeam Legend
VMware vExpert
Follow me
Thank you for another great article. The place else may just anyone get that type of
information in such a perfect method of writing?
I’ve a presentation next week, and I’m on the look for such information.
Nice weblog here! Also your web site rather a lot up fast!
What host are you the usage of? Can I get your affiliate hyperlink for your host?
I desire my web site loaded up as fast as yours lol