Date: Mon, 20 Jun 2022 02:39:44 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 264779] local_unbound not using correct name servers after install Message-ID: <bug-264779-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264779 Bug ID: 264779 Summary: local_unbound not using correct name servers after install Product: Base System Version: 13.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: freebsd@winter.cafe After both setting custom name servers and enabling local_unbound during install, local_unbound's setup script does not use the name servers I set to generate the forwarder configuration. However, the /etc/resolv.conf.bak file that the setup script created contains the correct name servers, so I have = no clue where exactly it got the incorrect name servers from. To reproduce: 1. Set custom name servers during bsdinstall, as well as enable local_unbou= nd 2. Observe that incorrect name servers are specified in /etc/unbound/forward.conf Something peculiar that I think is worth noting is that the generated forwa= rd configuration contains "# Generated by resolvconf", and local_unbound's set= up script creates a resolvconf configuration file. So it looks like these two processes are clashing, since resolvconf overrides the forward configuration that local_unbound's setup script generates. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264779-227>