I have a Debian 11 VM. I have something really weird happening regarding it with the Adguard Home Plugin via OPNsense. When I set this one VM nameservers to point at the Adguard plugin 192.168.1.1 it doesn't connect. I can ping 8.8.8.8 but not google.com. Now this is where it gets odd...if I set the nameservers to any out going server the VM then uses Adguard Home. Basically if I set the DNS nameservers to Adguard I can't go anywhere online unless I know the IP #. If I set the nameservers to external servers I can go to a ad test site and it's blocking as expected. FYI I also have unbound setup as a local resolver listening on 5353.
Is this VM using the host nameserver? That would explain why it doesn't like when I set the nameserver as 192.168.1.1 and why it's not resolving when I try to set an external namerserver? But how do I stop it from using the host nameserver? I have another Debian VM that was started the day before this one with nearly identical settings and the older one uses the Adguard nameservers just fine.
FYI when i reboot the VM my nameservers reset to the Adguard one. I had to chattr the etc/resolv.conf to point to external servers to get connection and to apparently use Adguard.
Is this VM using the host nameserver? That would explain why it doesn't like when I set the nameserver as 192.168.1.1 and why it's not resolving when I try to set an external namerserver? But how do I stop it from using the host nameserver? I have another Debian VM that was started the day before this one with nearly identical settings and the older one uses the Adguard nameservers just fine.
FYI when i reboot the VM my nameservers reset to the Adguard one. I had to chattr the etc/resolv.conf to point to external servers to get connection and to apparently use Adguard.
Last edited: