How do you configure DNS for a Route host and ensure external users can reach the Route?

• A. DNS is not required; Route works without DNS.
• B. Configure NodePort to expose Route.
• C. Set spec.host to the desired DNS; configure DNS to point to the OpenShift router's external IP; ensure TLS/Route type is configured as needed.
• D. Set the Route to public by default; nothing else needed.

Answer: (C)

OpenShift Routes rely on DNS to map a user-friendly host to the cluster router. The host you want users to reach must be set in the Route as spec.host. Then you point DNS so that that hostname resolves to the OpenShift router’s external IP. When external clients resolve that name and send requests to the router, the router matches the host in the request and forwards it to the appropriate service.

If you need TLS, configure the route’s TLS termination type (edge, reencrypt, or passthrough) and provide the necessary certificate configuration so clients trust the cert and encryption is handled as you intend. This combination—proper host in the Route, DNS pointing to the router, and correct TLS/termination settings—ensures external users can reach the Route reliably.

Other approaches aren’t correct because bypassing DNS or exposing the service via NodePort doesn’t leverage the Route’s host-based routing, and assuming everything is public without DNS and TLS setup won’t work for external access.