Description of problem:
Any chance this commit  can be back-ported to OCP 4.4.z ??
Bug 1809611: OpenStack: Set coredns forward policy to sequencial
The default policy for CoreDNS forward plugin being random , the
cluster may not be able to resolve the OpenStack API hostname when the
user sets multiple external DNS resolvers such as
['172.31.8.1','126.96.36.199'], where 172.31.8.1 knows to resolve internal
hostnames and 188.8.131.52 is a public resolver that doesn't know how to
resolve internal hostnames.
Switch to the sequencial policy to simulate the libc behavior and not
surprise users who expect the DNS servers specified via `externalDNS`
option to have a hierarchy.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure DNS forwarding as per  and want to access an external registry with a FQDN only known in the forwarded zones.
NXDOMAIN for internal hostnames that need forwarding to select upstream servers for resolving.
Hostnames in forwarded zones are resolvable via Coredns on node(s)
*** Bug 1851911 has been marked as a duplicate of this bug. ***
Verified on 4.4.0-0.nightly-2020-07-04-120349
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.