Unbound is not using dns ip address received using dhcp even if using openresolv

[dummys]

I'm wondering if it should work like this or not.
My configuration is: Arch linux with NetworkManager + openresolv + unbound as local resolver/cache.
the config are the following:

/etc/NetworkManager/conf.d/rc-managert.conf -> rc-manager=resolvconf
/etc/unbound/unbound.conf include: /etc/unbound-resolvconf.conf
/etc/resolvconf.conf:

name_servers=127.0.0.1
unbound_config=/etc/unbound-resolvconf.conf
private_interfaces="*"

When connecting to a new network, i check resolvconf using resolvconf -l and I get two differents local ip for dns server.
when I check the file /etc/unbound-resolvconf.conf, I see nothing inside, just the file is created.
Inside my /etc/resolv.conf i get: nameserver 127.0.0.1 and I also protected it using chattr +i

For me the behavior I should have is that the unbound-resolvconf.conf should be populated with the dns ip server from the dhcp.

System:

• Unbound version: 1.19.0
• OS: Arch linux up to date
• unbound -V output:

Configure line: --prefix=/usr --sysconfdir=/etc --localstatedir=/var --sbindir=/usr/bin --disable-rpath --enable-dnscrypt --enable-dnstap --enable-pie --enable-relro-now --enable-subnet --enable-systemd --enable-tfo-client --enable-tfo-server --enable-cachedb --with-libhiredis --with-conf-file=/etc/unbound/unbound.conf --with-pidfile=/run/unbound.pid --with-rootkey-file=/etc/trusted-key.key --with-libevent --with-libnghttp2 --with-pyunbound
Linked libs: libevent 2.1.12-stable (it uses epoll), OpenSSL 3.2.0 23 Nov 2023
Linked modules: dns64 cachedb subnetcache respip validator iterator
DNSCrypt feature available
TCP Fastopen feature available