Stork cannot parse named.conf with multiple allow addresses in inet_spec

From the mailing list:

I am testing out using Stork for BIND9 in a lab environment. I can connect to the Stork Agent running on the BIND server without any problems, but Stork never shows the DNS service as running. I have verified that BIND is running.

When I check messages on the BIND server, I see the following:

Sep 21 14:46:22 bind_server stork-agent: #033[33mWARN#033[0m[2020-09-21 14:46:22]            bind9.go:284   cannot parse BIND 9 statistics-channels clause
Sep 21 14:46:32 bind_server stork-agent: #033[33mWARN#033[0m[2020-09-21 14:46:32]            bind9.go:91    cannot parse BIND 9 inet configuration: no match (controls {

The config syntax is valid from BIND's perspective. Does Stork have requirements above and beyond that?

Thanks!

Details: BIND: 9.11.4 Stork: 0.11.0

Controls Clause of bind config:

controls {
        inet 127.0.0.1 allow { localhost; };
        inet * allow {localhost; 10.50.0.100; 10.50.0.105; };
};

Statistics Channel clause of bind config:

statistics-channels {
        inet 10.50.0.105 port 80 allow { localhost; 10.50.0.100; 10.50.0.105; };
};