1. Proposed title of this feature request

•  DNS forwarder should work on the nodes themselves

2. What is the nature and description of the request?

• if you use DNS forwarding and you attempt to deploy a pod that relies on an image resolvable only via that external DNS forwarding, the container will fail to start, as DNS forwarding only applies in requests to CoreDNS, not to the node itself. 
• that seems to be an known issue: cri-o doesn't use the cluster DNS service, so unless an image registry can be resolved using /etc/hosts or a resolver in /etc/resolv.conf, it will not be possible to pull images from that registry.

3. Why does the customer need this? (List the business requirements here)

• 
  We need the worker nodes to forward DNS queries for our internal domains to our internal DNS servers as per the current DNS operator configuration.

4. List any affected packages or components.

• openshift-dns-operator
• CoreDNS forward plugin