How do I configure dns over tls DOT unbound

I have been trying to get unbound working with DOT dns over TLS but my config file needs a lot of work. Here is my current config file Code:root@odroid64:~# cat /etc/unbound/unbound.conf
server:
# If no logfile is specified, syslog is used
# logfile: "/var/log/unbound/unbound.log"
verbosity: 0

interface: 127.0.0.1
port: 5335
do-ip4: yes
do-udp: yes
do-tcp: yes

# May be set to yes if you have IPv6 connectivity
do-ip6: no

# Use this only when you downloaded the list of primary root servers!
# If you use the default dns-root-data package, unbound will find it automatically
root-hints: "/var/lib/unbound/root.hints"

# Trust glue only if it is within the server's authority
harden-glue: yes

# Require DNSSEC data for trust-anchored zones, if such data is absent, the zone becomes BOGUS
harden-dnssec-stripped: yes

# Don't use Capitalization randomization as it known to cause DNSSEC issues sometimes
# see https://discourse.pi-hole.net/t/unbound-stubby-or-dnscrypt-proxy/9378 for further details
use-caps-for-id: no

# Reduce EDNS reassembly buffer size.
# Suggested by the unbound man page to reduce fragmentation reassembly problems
edns-buffer-size: 1472

# Perform prefetching of close to expired message cache entries
# This only applies to domains that have been frequently queried
prefetch: yes

# One thread should be sufficient, can be increased on beefy machines. In reality for most users running on small networks or on a single machine, it should be unnecessary to seek performance enhancement by increasing num-threads above 1.
num-threads: 1

# Ensure kernel buffer is large enough to not lose messages in traffic spikes
so-rcvbuf: 1m

# Ensure privacy of local IP ranges
private-address: 192.168.0.0/16
private-address: 169.254.0.0/16
private-address: 172.16.0.0/12
private-address: 10.0.0.0/8
private-address: fd00::/8
private-address: fe80::/10
forward-zone:
name: "."
forward-tls-upstream: yes
forward-addr: 1.1.1.1@853#cloudflare-dns.com
forward-addr: 1.0.0.1@853#cloudflare-dns.comHowever it's not working as you can see from the systemctl status unbound. What can I do to this config file that DOT works.
Code:root@odroid64:~# systemctl status unbound
unbound.service
Loaded: loaded (/etc/init.d/unbound; bad; vendor preset: enabled)
Drop-In: /run/systemd/generator/unbound.service.d
50-insserv.conf-$named.conf, 50-unbound-$named.conf
Active: active (exited) since Thu 2021-07-15 16:37:20 CEST; 7s ago
Docs: man:systemd-sysv-generator(8)
Process: 23973 ExecStop=/etc/init.d/unbound stop (code=exited, status=0/SUCCESS)
Process: 24057 ExecStart=/etc/init.d/unbound start (code=exited, status=0/SUCCESS)

Jul 15 16:37:20 odroid64 unbound[24057]: * Starting DNS server unbound
Jul 15 16:37:20 odroid64 unbound-anchor[24076]: /var/lib/unbound/root.key has content
Jul 15 16:37:20 odroid64 unbound-anchor[24076]: success: the anchor is ok
Jul 15 16:37:20 odroid64 unbound[24057]: /etc/unbound/unbound.conf:54: error: unknown keyword 'forward-tls-upstream
Jul 15 16:37:20 odroid64 unbound[24057]: /etc/unbound/unbound.conf:54: error: stray ':'
Jul 15 16:37:20 odroid64 unbound[24057]: /etc/unbound/unbound.conf:54: error: unknown keyword 'yes'
Jul 15 16:37:20 odroid64 unbound[24057]: read /etc/unbound/unbound.conf failed: 3 errors in configuration file
Jul 15 16:37:20 odroid64 unbound[24057]: [1626359840] unbound[24080:0] fatal error: Could not read config file: /etc/unbound/unbound.conf
Jul 15 16:37:20 odroid64 unbound[24057]: ...fail!
Jul 15 16:37:20 odroid64 systemd[1]: Started unbound.service.