Comment 26 for bug 1821026

Hi all,

The similar problem is reported here:
https://github.com/coredns/coredns/issues/2830

The default policy for forward which facilitates proxying DNS messages to upstream resolver is random. It means that multiple upstreams are randomized (see policy) on first use. In this bug, 10.248.2.1 maybe chosen and 10.248.2.1 can't resolve compute-0.
https://github.com/coredns/coredns/tree/master/plugin/forward

Another possible solution: change the policy of forward from random to sequential which selects hosts based on sequential ordering. (Note 192.178.204.2 is the first dns server in /etc/resolv.conf).