configure:20735: checking for nsupdate configure:20753: found /usr/bin/nsupdate configure:20765: result: /usr/bin/nsupdate configure:20773: checking for executable nsupdate configure:20781: result: yes configure:20784: checking for nsupdate 'realm' support' configure:20786: echo realm |$NSUPDATE >&2 parse of /etc/resolv.conf failed configure:20789: $? = 1 configure:20794: result: no configure:20796: error: nsupdate does not support 'realm' With FEATURES=-network-sandbox, this test succeeds: configure:20735: checking for nsupdate configure:20753: found /usr/bin/nsupdate configure:20765: result: /usr/bin/nsupdate configure:20773: checking for executable nsupdate configure:20781: result: yes configure:20784: checking for nsupdate 'realm' support' configure:20786: echo realm |$NSUPDATE >&2 configure:20789: $? = 0 configure:20791: result: yes This is related to bug #675154 which happens to trigger the failure to parse resolv.conf: otherwise the forbidden network access would probably not be triggered by nsupdate.
I have net-dns/bind-tools-9.14.8 installed and still sys-auth/sssd-2.2.3-r1 fails to configure with: configure: error: nsupdate does not support 'realm'
still happening. workaround w/ -network-sandbox works, too.
What does /etc/resolv.conf contain on your system?
(In reply to Mike Gilbert from comment #3) > What does /etc/resolv.conf contain on your system? $ cat /etc/resolv.conf # Generated by dhcpcd from br0.dhcp, br0.ra # /etc/resolv.conf.head can replace this line domain example.com nameserver 10.1.0.1 nameserver fe80::12fe:edff:fe89:3db0%br0 # /etc/resolv.conf.tail can replace this line