[Bug 247305] dns/unbound: start earlier because it can provide local name service

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 247305
           Summary: dns/unbound: start earlier because it can provide
                    local name service
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: avg at FreeBSD.org
                CC: jaap at NLnetLabs.nl
                CC: jaap at NLnetLabs.nl
             Flags: maintainer-feedback?(jaap at NLnetLabs.nl)

Created attachment 215610
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215610&action=edit
proposed patch

Rationale.

I am configuring a small LAN -- mostly a gateway / router for it -- and I am
using unbound for a local DNS and isc-dhcp44-server for DHCP.
I have a few hosts with static IP addresses (for various reasons).
So, in unbound.conf I have an entry like
  local-data: "hipster.home.arpa. IN A 192.168.0.222"

and in dhcpd.conf  have:
  host hipster {
    hardware ethernet 40:74:e0:xx:xx:xx;
    fixed-address hipster.home.arpa;
 }

I am using a DNS name to avoid hardcoding the same IP address twice.
But obviously this depends on the local DNS server starting before the HDCP
server if they are on the same host / router.
It seems that at the moment there is nothing to ensure that order.

It's been pointed out that both local_unbound and bind (in the default
configuration) start earlier.  local_ubound start even before NETWORKING while
bind starts before SERVERS.

I am proposing to change unbound port to do the same thing as bind ports.
START_LATE port option is provided for those who would need to start unbound at
its traditional stage.

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