include statement usage doesn't work as per documentation

Summary

There is either an outdated documentation for include statement or a bug in bind. The docs for include statement https://bind9.readthedocs.io/en/v9.16.37/reference.html#include-statement-definition-and-usage says:

The include statement inserts the specified file (or files if a valid glob expression is detected) at the point where the include statement is encountered

This is not actually working. Including config files in named.conf using a glob expression like '/etc/bind/custom/*.conf` fails with:

/etc/bind/named.conf:11: open: /etc/bind/custom/*.conf: file not found

BIND version used

root@ip-172-31-34-152:/etc/bind# named -v
BIND 9.16.37-Debian (Extended Support Version) <id:2b2afb2>

Steps to reproduce

Include in named.conf a file using glob expression eg: /etc/bind/custom/*.conf

What is the current bug behavior?

bind and named-checkconf fails to include files using the glob statement as per documentation

What is the expected correct behavior?

include statement using the glob expression should not fail.

Relevant configuration files

N/A

Relevant logs and/or screenshots

root@ip-172-31-34-152:/etc/bind# ls /etc/bind/custom/
custom.conf

root@ip-172-31-34-152:/etc/bind# named-checkconf 
/etc/bind/named.conf:11: open: /etc/bind/custom/*.conf: file not found
root@ip-172-31-34-152:/etc/bind#

Possible fixes

(If you can, link to the line of code that might be responsible for the problem.)