There is nothing specific to do as "forwarding" is an extra specific feature not needed for normal operations. Just enable recursion in bind and do not set up any zones in it, it will then be a recursive nameserver. You might also want to explore simpler alternatives, like unbound.
A recursive nameserver will do iterative queries to get the final answer. Forwarding queries is an edge case for very specific needs, or if you want to share caches/have a hierarchy of caches.
See RFC 8499 on "DNS Terminology":
Recursive mode: A resolution mode of a server that receives DNS
queries and either responds to those queries from a local cache or
sends queries to other servers in order to get the final answers
to the original queries.
Recursive resolver: A resolver that acts in recursive mode. In
general, a recursive resolver is expected to cache the answers it
receives (which would make it a full-service resolver), but some
recursive resolvers might not cache.
[..]
Forwarding: The process of one server sending a DNS query with the
RD bit set to 1 to another server to resolve that query.
Forwarding is a function of a DNS resolver; it is different than
simply blindly relaying queries.
Forwarder: Section 1 of [RFC2308] describes a forwarder as "a
nameserver used to resolve queries instead of directly using the
authoritative nameserver chain". [RFC2308] further says "The
forwarder typically either has better access to the internet, or
maintains a bigger cache which may be shared amongst many
resolvers." That definition appears to suggest that forwarders
normally only query authoritative servers. In current use,
however, forwarders often stand between stub resolvers and
recursive servers. [RFC2308] is silent on whether a forwarder is
iterative-only or can be a full-service resolver.
