nsdispatch errors on security/spiped when mdns lookups are enabled

[Dave Cottlehuber <dch@skunkwerks.at>]

[reposted from https://forums.freebsd.org/threads/58413/#post-333984
after validating my mdns setup]

I am getting lots of errors in my logfiles using security/spiped
(v1.5.0_1 on FreeBSD 11.0 amd64). NB spiped is not using mdns-based
addresses specifically, only IPv4 or FQDN.

2016-11-06T10:17:00.398940+00:00 wintermute spiped:
NSSWITCH(_nsdispatch): mdns_minimal, hosts, getaddrinfo, not found, and
no fallback provided
2016-11-06T10:17:19.095431+00:00 wintermute spiped:
NSSWITCH(_nsdispatch): mdns_minimal, hosts, getaddrinfo, not found, and
no fallback provided
...

# /etc/nsswitch.conf
# nsswitch.conf(5) - name service switch configuration file
# $FreeBSD: releng/11.0/etc/nsswitch.conf 301711 2016-06-09 01:28:44Z
markj $
#
group: files
hosts: files mdns_minimal [NOTFOUND=return] dns mdns
networks: files
passwd: files
shells: files
services: files
protocols: files
rpc: files

Switching to the simpler:

hosts: files dns mdns

resolve the spiped-related issue but presumably generates failing MDNS
requests for .local domains to root nameservers, which is undesirable.
http://0pointer.de/lennart/projects/nss-mdns/ suggests the above format
is reasonable.

Is there anything I can do here to have the best of both worlds (working
mdns, no root server spam, & happy spiped with tidy logs)?

BTW spiped configs look like this:

spiped_pipes="${spiped_pipes} COUCHDB_PRIMARY COUCHDB_BACKUP"
spiped_pipe_COUCHDB_PRIMARY_mode="client"
spiped_pipe_COUCHDB_PRIMARY_source="127.0.0.1:5984"
spiped_pipe_COUCHDB_PRIMARY_target="c1.skunkwerks.at:45984"
spiped_pipe_COUCHDB_PRIMARY_key="/usr/local/etc/spiped/couchdb.key"
spiped_pipe_COUCHDB_BACKUP_mode="client"
spiped_pipe_COUCHDB_BACKUP_source="127.0.0.1:5985"
spiped_pipe_COUCHDB_BACKUP_target="c2.skunkwerks.at:45984"
spiped_pipe_COUCHDB_BACKUP_key="/usr/local/etc/spiped/couchdb.key"

Thanks
Dave