On 2022-04-20 01:21:23 +0300, Michael Tokarev wrote: > 20.04.2022 00:55, Vincent Lefevre wrote: > > If I stop unbound, then I still get hostname resolution. But if I only > > have > > > > nameserver 127.0.0.1 > > > > and unbound is stopped, then hostname resolution no longer works. > > This shows that 192.168.1.1 is used as a fallback. > > So this is all about resolvconf: it should have a way to treat some > nameservers as "fallback-only" and not propagate them to local nameservers.
Yes, I recall that I initially reported the bug against resolvconf. But Andrej Shadura eventually reassigned it to unbound, implying that unbound was doing that with its resolvconf integration. So this is really confusing. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
