[Bug 194975] New: dns/dnscrypt-proxy should start before local_unbound

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 194975
           Summary: dns/dnscrypt-proxy should start before local_unbound
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: jrm at ftfl.ca
                CC: freebsd at dns-lab.com
                CC: freebsd at dns-lab.com
             Flags: maintainer-feedback?(freebsd at dns-lab.com)

Created attachment 149341
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149341&action=edit
add # BEFORE: local_unbound to files/dnscrypt-proxy.in

A 10.x system running dns/dnscrypt_proxy as a forwarder for a local_unbound
cache hang because some services (e.g. ntpd or sysutils/bsdstats) can't resolve
hostnames until dns/dnscrypt_proxy has started.  The attached patch adds 

# BEFORE: local_unbound

to files/dnscrypt-proxy.in.

Is a warning required here since things work differently (named on 9.x,
local_unbound on 10.x)?  bdrewery mentioned a warning might be useful.

--- Comment #1 from Bugzilla Automation <bugzilla at FreeBSD.org> ---
Maintainer CC'd

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