[Bug 221920] local_unbound NOT working

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221920

            Bug ID: 221920
           Summary: local_unbound NOT working
           Product: Base System
           Version: 11.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: joeb1 at a1poweruser.com

1. The first time startup logic has usage problem. Requires the
"local_unbound_enable="YES" statement in rc.conf and a reboot to create the
correct files on first time setup.

2. When stopping unbound the /etc/resolv.conf created by unbound needs to be
replaced with the saved original version so dns lookups will still work. That
means that on unbound startup the unbound version of the /etc/resolv.conf has
to be swapped back into place. The/etc/rc.d/local_unbound script needs to be
changed adding this function.

3.The logfile: verbosity: and local-zone: parameters of the
/var/unbound/unbound.conf file do not work. Maybe these are compile time
options that need to be enabled when the local_unbound binary was created.

4. The /usr/sbin/local-unbound-setup script needs to be changed in
gen_resolvconf_conf() section replacing
echo "unbound_conf=\"${forward_conf}\""
with
echo "unbound_conf=\"${unbound_conf}\""

I did the number 4 change and then did "service local_unbound start". Ps ax
shows local_unbound running. I have the built in version of ntpd running and
keep getting this message repeated all day long
Aug 29 10:11:35 testsys ntpd[952]: error resolving pool 0.freebsd.poo
l.ntp.org: hostname nor servname provided, or not known (8)

When I try to run any svn download job I get this message
svn: E170013: Unable to connect to a repository at URL
'svn://svn.freebsd.org/po
rts/head/sysutils/qjail'
svn: E670008: Unknown hostname 'svn.freebsd.org'

When I issue "service local_unbound stop" and followed by number 2, the normal
dns environment started working and everything is good again.  

The above error messages do not show up when local_unbound is off, so must be
problem with local_unbound.

I can not see how this new built in function has ever worked.

-- 
You are receiving this mail because:
You are the assignee for the bug.