// Module included in the following assemblies:
//
// * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc

:_mod-docs-content-type: REFERENCE
[id="hcp-ibm-z-dns_{context}"]
= DNS configuration for {hcp} on {ibm-z-title}

[role="_abstract"]
The API server for the hosted cluster is exposed as a `NodePort` service. A DNS entry must exist for the `api.<hosted_cluster_name>.<base_domain>` that points to the destination where the API server is reachable.

The DNS entry can be as simple as a record that points to one of the nodes in the managed cluster that is running the hosted control plane.

The entry can also point to a load balancer deployed to redirect incoming traffic to the Ingress pods.

See the following example of a DNS configuration:

[source,terminal]
----
$ cat /var/named/<example.krnl.es.zone>
----

.Example output
[source,terminal]
----
$ TTL 900
@ IN  SOA bastion.example.krnl.es.com. hostmaster.example.krnl.es.com. (
      2019062002
      1D 1H 1W 3H )
  IN NS bastion.example.krnl.es.com.
;
;
api                   IN A 1xx.2x.2xx.1xx
api-int               IN A 1xx.2x.2xx.1xx
;
;
*.apps        IN A 1xx.2x.2xx.1xx
;
;EOF
----
The `api` record refers to the IP address of the API load balancer that handles ingress and egress traffic for {hcp}.

For {ibm-title} z/VM, add IP addresses that correspond to the IP address of the agent.

[source,terminal]
----
compute-0              IN A 1xx.2x.2xx.1yy
compute-1              IN A 1xx.2x.2xx.1yy
----
