Comment 9 for bug 2055776

After starting named with my named.conf.options setting, I manually generated virbr0 with brctl and set the IP address (192.168.122.1), and named started listening to 192.168.122.1 using TCP.

$ cat /etc/bind/named.conf.options
options {
  directory "/var/cache/bind";

  // If there is a firewall between you and nameservers you want
  // to talk to, you may need to fix the firewall to allow multiple
  // ports to talk. See http://www.kb.cert.org/vuls/id/800113

  // If your ISP provided one or more IP addresses for stable
  // nameservers, you probably want to use them as forwarders.
  // Uncomment the following block, and insert the addresses replacing
  // the all-0's placeholder.

  // forwarders {
  // 0.0.0.0;
  // };

  //========================================================================
  // If BIND logs error messages about the root key being expired,
  // you will need to update your keys. See https://www.isc.org/bind-keys
  //========================================================================
  dnssec-validation auto;
  listen-on port 53 { localhost; 192.168.122.0/24; };
  allow-query { localhost; 192.168.122.0/24; };
};
$

Because of this behavior, I think that the operations of dnsmasq and named conflicted, resulting in an error on the dnsmasq side(the second make_sock() with SOCK_STREAM).

This named is started because it is necessary, but I understand that the VM host should not run many processes, so the name resolution function is not run on the VM host, but on another I'm planning to move to a server.

I understood where the problem is. Thank you very much for your cooperation.
I initially reported it as a bug in dnsmasq, but it turned out to be a problem in my environment.