Use Quad9 for Proxmox; root DNS for Unbound, or let Proxmox host be Unbound's DNS resolver; ADH inherits Unbound's DNS.

Root DNS > Unbound or use Proxmox's IP for UnboundUnbound > ADH

Your current setup works for now because DNS is cached or you have a fallback DNS for Unbound. If it's the former, it will break, if it's the latter, it won't.

(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

(Quote)

This is utterly preposterous! An eight-euro one-time fee for the registry lock, and should I need to update the DNS record and reactivate the registry lock, I must pay yet another eight euros!

REVERSE DNS MANAGEMENT IN ALL OUR LOCATIONS FROM THE VPS/DEDICATED CONTROL PANEL.

Fly lets you deploy what you want quickly. Bunny does the same. Bunny has a beautiful interface for it (props to their team). They both let you deploy on the edge but you have to build your own stack

No real reason for the current setup except it just works. I installed proxmox and then ADH lxc. I've put dns for proxmox to be ADH IP with no particular reason. Yesterday I've added Unbound (been usi

Public DNS > Proxmox hostRoot DNS > Unbound or use Proxmox's IP for UnboundUnbound > ADH

OP states it is not public and CH states it was in public_html, someone needs to be clear does anything resolve to the listening name or are dummy records being used when DNS is created.

If someone's using a proxmox with adguard home and unbound lxc, should proxmox and unbound lxc have adguard home's IP as their DNS?