Hi, Sorry about the late response, notification seems to have failed too.
To produce outputs that you requested, I did some tests. test$ resolvconf -l # resolv.conf from tun10.openvpn search test1.example.org example.org test2.example.org nameserver 192.168.1.1 # resolv.conf from wlan0 # resolv.conf for wlan0 domain test2.example.org search test2.example.org. example.org. test1.example.org nameserver 192.168.0.1 test$ resolvconf -v DOMAIN='test2.example.org' SEARCH='test test1.example.org example.org test2.example.org test2.example.org. example.org. test1.example.org.' NAMESERVERS='192.168.0.1' LOCALNAMESERVERS='' DOMAINS='test1.example.org:192.168.1.1 example.org:192.168.1.1 test2.example.org:192.168.1.1 test2.example.org.:192.168.0.1 example.org.:192.168.0.1 test1.example.org.:192.168.0.1' The bug seems linked with the dot at the end of domain names. When all entries have the same syntax, it works ! Can you add the trailing dot when it's not present ? It will limit DNS queries with suffixes in /search/ (without that, a combination of suffixes is tried for each query). Otherwise, I do not think this is the best solution to merge resolvers addresses provided by the various network interfaces for a zone. Indeed, if the zone is the same on all networks, there is no problem. But if not, wouldn't it cause strange behaviors, like not predictable mixed resolutions, induced by timeouts for example ? In my opinion, we should only have access to one zone at a time, the one provided by the highest priority interface for example. However, it would be useful to keep the fusion for resolvers on the same interface, provided by different sources like DHCP and DHCPv6... What do you think ? Best regards, Thibaut Chèze
signature.asc
Description: OpenPGP digital signature
