1. Proposed title of this feature request
Add custom A/AAAA records to CoreDNS in OpenShift allowing the ability to have self-managed DNS records, without requiring an upstream DNS server.

2. What is the nature and description of the request?
The `pod.spec.hostAliases` value can be used to inject Host-values into the `/etc/hosts` file of a Kubernetes Pod. After this, all requests are forwarded to the OpenShift-controller CoreDNS service.

It will be useful is we can add DNS rules into the CoreDNS service, such as defining A records using custom domains other than `cluster.local`.

This could be achieved by leveraging the `hosts` CoreDNS Plugin and the `spec.hostAliases` values, providing more control over the DNS resolution process in OpenShift.

3. Why does the customer need this? (List the business requirements here)
To allow business domains to become accessible from inside OpenShift without directing all OpenShift DNS traffic to the enterprise DNS servers.

4. List any affected packages or components.
CoreDNS, OpenShift Cluster DNS Operator