Comment 24 for bug 1821026

Hi matt,
I tried to verify your submitted, but the test show all DNS resolutions that are not within k8s will go through dnsmasq.
the coredns-resolv.conf file show as below.
----------------------------------------------------------------------------------
[sysadmin@controller-0 ~(keystone_admin)]$ cat resolv.conf # this file copy from coredns pod.
nameserver 192.178.204.2 # dnsmasq listen on 192.178.204.2:53
nameserver 10.248.2.1
----------------------------------------------------------------------------------
the coredns will use dnsmasq as a upstream dns server when resolving domain that not within k8s.
the host interface also can receive some dns require when tupdump listen to 192.178.204.2:53.
...
08:41:35.573214 IP controller-1.45569 > controller.domain: 3673+ A? compute-1. (27)
08:41:35.573350 IP controller.domain > controller-1.45569: 3673* 1/0/0 A 192.178.204.39 (43)
...

Is it possible that the problem appears on dnsmasq? Do you have any suggestions?

Hi Peng,
Could you please try to reproduce this bug with the latest build? I`ve tried many times, but it`s hard to duplicate this bug.
when you duplicate it in your environment, please check that the host, such as controller-0, can ping compute-0 or compute-1 directly.
this is to verify that dnsmasq is working. thx~