@girish
I updated the forward-everything.conf to point to my router and got the same results. unbound status also had the same errors.
I did a ping of api.namecheap.com from my regular desktop, and it seemed to worked normally (maybe not useful info lol).
I then tried pointing the forward-everything.conf to the DNS address listed in my router (the modem from my ISP forwards everything to the router). Using that changed the status results of unbound but the ping to api.namecheap.com still didn't work unfortunately.
Results from forwarding to DNS address listed in router:
alphy@cloud-alphy:~$ ping api.namecheap.com
ping: api.namecheap.com: Name or service not known
alphy@cloud-alphy:~$ systemctl status unbound
● unbound.service - Unbound DNS Resolver
Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor prese>
Active: active (running) since Fri 2024-01-12 16:34:39 UTC; 27s ago
Main PID: 6907 (unbound)
Tasks: 1 (limit: 34650)
Memory: 7.0M
CPU: 56ms
CGroup: /system.slice/unbound.service
└─6907 /usr/sbin/unbound -d
Jan 12 16:34:39 cloud-alphy systemd[1]: Starting Unbound DNS Resolver...
Jan 12 16:34:39 cloud-alphy unbound[6907]: [6907:0] notice: init module 0: subn>
Jan 12 16:34:39 cloud-alphy unbound[6907]: [6907:0] notice: init module 1: vali>
Jan 12 16:34:39 cloud-alphy unbound[6907]: [6907:0] notice: init module 2: iter>
Jan 12 16:34:39 cloud-alphy unbound[6907]: [6907:0] info: start of service (unb>
Jan 12 16:34:39 cloud-alphy systemd[1]: Started Unbound DNS Resolver.
Jan 12 16:34:51 cloud-alphy unbound[6907]: [6907:0] info: generate keytag query