I never use su because my root accounts dont have a password set and thus are less susceptible to brute force attacks etc.
When working with a non-root account and sudo allows me to more easily switch to other users for testing that might not have Bash configured as a shell like for example the www-data user eg:
sudo -u USER COMMAND
The steps in the article to set the root password, if so desire, can be shortened to:
sudo passwd
Or:
sudo passwd root
Below some more incentives to not use su or sudo -i:
Almost all the magic is done through DNS.
There are but few web sites that detect this kind of DNS blocking but Pi-hole got an on/off switch for that (have to clear all cache!).
Pi-hole doesnt touch the net content like with for example routing or proxying.
So you wont be able to redirect content with Pi-hole (alone).
But almost anything is possible with Linux.
Authored Comments
I never use su because my root accounts dont have a password set and thus are less susceptible to brute force attacks etc.
When working with a non-root account and sudo allows me to more easily switch to other users for testing that might not have Bash configured as a shell like for example the www-data user eg:
sudo -u USER COMMAND
The steps in the article to set the root password, if so desire, can be shortened to:
sudo passwd
Or:
sudo passwd root
Below some more incentives to not use su or sudo -i:
https://wiki.debian.org/sudo
Almost all the magic is done through DNS.
There are but few web sites that detect this kind of DNS blocking but Pi-hole got an on/off switch for that (have to clear all cache!).
Pi-hole doesnt touch the net content like with for example routing or proxying.
So you wont be able to redirect content with Pi-hole (alone).
But almost anything is possible with Linux.