DNS forwarding fails for private registry lookup

[njayakrishna]

Hi,
After the OKD cluster is setup, I see the following is failing:

1. crictl pull of an image from private registry fails. The private registry has been added appropriately to /etc/containers/registries.conf and the server certificate of the registry is placed in /etc/ssl/certs and ca-trust updated.
   The error is that it is not able to lookup the private registry
   dial tcp: lookup registry.xyz.net on 10.0.0.253:53: no such host.
   As expected curl also fails for the registry.
2. But the image pull from internet site like docker.io works fine.
   While I installed the cluster I did set the environment variable KUBEINIT_COMMON_DNS_PUBLIC to the DNS server of the network I am in. I am able to ping to that DNS server as well. The same is also set appropriately in the script installation as well as in the /etc/resolv.conf in the helper node:
   [root@service ~]# cat /etc/resolv.conf
   search okdcluster.kubeinit.local
   nameserver 10.0.0.253
   nameserver 135.250.39.11

can you please let me know how to solve this issue? Is it something I need to add for bind service in the bind container running on the hypervisor?

Thanks
Jayakrishna

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days