Skip to content

Latest commit

 

History

History
46 lines (34 loc) · 1.99 KB

ref_dns-configuration.adoc

File metadata and controls

46 lines (34 loc) · 1.99 KB
Raw

DNS configuration details

General DNS setup

The OpenShift cluster managed by {prod} uses 2 DNS domain names, crc.testing and apps-crc.testing. The crc.testing domain is for core OpenShift services. The apps-crc.testing domain is for accessing OpenShift applications deployed on the cluster.

For example, the OpenShift API server will be exposed as api.crc.testing while the OpenShift console is accessed through console-openshift-console.apps-crc.testing. These DNS domains are served by a dnsmasq DNS container running inside the {prod} virtual machine.

Running {bin} setup will adjust your system DNS configuration so that it can resolve these domains. Additional checks are done to verify DNS is properly configured when running {bin} start.

Linux

On Linux, {prod} expects the following DNS configuration:

  • {prod} expects NetworkManager to manage networking.

  • NetworkManager uses dnsmasq via the /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf configuration file.

  • The configuration file for this dnsmasq instance is /etc/NetworkManager/dnsmasq.d/crc.conf:

    server=/crc.testing/192.168.130.11
server=/apps-crc.testing/192.168.130.11

    • The NetworkManager dnsmasq instance forwards requests for the crc.testing and apps-crc.testing domains to the 192.168.130.11 DNS server.

{mac}

On {mac}, {prod} expects the following DNS configuration:

  • {prod} creates a /etc/resolver/testing file which instructs {mac} to forward all DNS requests for the testing domain to the {prod} virtual machine.

  • {prod} also adds an api.crc.testing entry to /etc/hosts pointing at the VM IP address. The oc binary requires this entry. See OpenShift issue #23266 for more information.