IBM Support

Cloud Pak for Security: Do not use “.local” as the Top-level domain(TLD) in nonpublic facing Red Hat OpenShift deployment for CP4S.

Question & Answer


Question

Why .local cannot be used as the top-level domain (TLD) in nonpublic facing Red Hat OpenShift installations for CP4S?

Cause

Using .local as a TLD for a nonpublic facing Red Hat OpenShift cluster setup, specifically in the planning phase, causes connectivity issues with internal DNS servers, DHCP servers, and several operating systems. These systems refuse to resolve the .local domain to IP addresses outside of the link-local reserved IP space of 162.254/16 or the equivalent IPv6 reserved space.
This issue is relevant for on premises, self-hosted, hybrid cloud and non-SaaS CP4S deployments.

Answer

Instead of using .local, use one of the following domains for nonpublic facing setups:
  • .test
  • .example
  • .invalid
  • .localhost

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTDPP","label":"IBM Cloud Pak for Security"},"ARM Category":[{"code":"a8m0z0000001h8uAAA","label":"Install or Upgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
10 June 2022

UID

ibm16593891

Page Feedback