libunbound not always picking the first nameserver in /etc/resolv.conf

Jiatong Shen yshxxsjt715 at
Wed Feb 16 00:12:17 UTC 2022

Dear community members,

  hello, I have a small question and would like to get some insights..I am
using openvswitch + sflow to connect network traffic and when posting data
openvswitch seems to not resolving address correctly. after some debugging,
I find that openvswitch uses libunbound to resolve dns and sometimes dns
resolve does not work. I check the /etc/resolve.conf file, and find that
there are dns nameservers configured and one of them cannot resolve the
given dns name (because it is local dns and is not global resolvable). but
the global dns is configured after the local nameserver, so in my opinion
it should have a higher priority. but looks like libunbound does not
respect the nameserver order.

 My question is is my observation correct? if it is correct, is there
anyway I can make libunbound to use dns nameservers in the order defined in
resolv.conf? thank you


Best Regards,

Jiatong Shen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Unbound-users mailing list