

Sorry I misread your post. You shouldn’t need the 172 address in your DNS config, stick to the 127 address only.
In regard to the issue itself. Do your devices show their DNS server as the adguard server?
Sorry I misread your post. You shouldn’t need the 172 address in your DNS config, stick to the 127 address only.
In regard to the issue itself. Do your devices show their DNS server as the adguard server?
Your adguard config looks strange. The examples shown list different DNS providers but you have pointed it back at itself for its DNS. I don’t understand why you would do that.
I use Arch because it makes installing almost any software package trivially easy via the AUR and if you run into issues, the wiki is there to help.
You should try out KDE in a Live CD. The snapping and tiling features work very well, Windows needs to catch up
It is paid for, with your time ;)
I came to Arch for the customisation, I stayed for the AUR
It sounds like this software was made to address a problem that exists in Windows, poor window management options. Although with Win11 it’s been significantly improved.
Have a look into tiling window managers, or tiling add-ons for major desktop environments. You can split windows in all different arrangements without any extra software or splitting inputs.
Personally I’m using KDE and it’s built in tiling options work very well.
I’m not very familiar with that software, what features does it have that you want to use?
Arch, nothing beats the availability and ease of installing packages from the AUR
That might explain the problem. Assuming adguard returns an nxdomain for blocked sites then the devices will try with their secondary DNS server and get to the blocked site