bind-tools 9.12.1: Parsing of /etc/resolv.conf fails with link-local IPv6 NS server address

Summary

On Linux, Freedesktop.org's NetworkManager (v 1.10.6) sometimes generates a /etc/resolv.conf file which only contains a single link-local IPv6 nameserver address:

# Generated by NetworkManager
nameserver fe80::1%wlp3s0

Bind-Tools fail to parse the file correctly while glibc tools (getent hosts...) or ping (via GNU inetutils) succeed:

 $ dig a isc.org                                                                                                                                                                                
dig: parse of /etc/resolv.conf failed

 $ ping isc.org
PING isc.org (149.20.64.69) 56(84) bytes of data.

(Same result for all Bind-Tools).

Steps to reproduce

Add a single IPv6 link-local nameserver entry to your resolv.conf

What is the current bug behavior?

Common bind-tools (dig, nslookup, host) fail to parse resolv.conf.

What is the expected correct behavior?

bind-tools should parse resolv.conf correctly regardless of what special IPv6 address format is used.

Relevant configuration files

/etc/resolv.conf.

Relevant logs and/or screenshots

Not applicable.

Possible fixes

No data.