Am not sure if thats recommended.
That would mean that if processes on the own host try to lookup their own name debianserver, they wont be able to connect without resorting to external DNS records.
And some use that line to configure the FQDN for the own host:
pi@ph5b:~ $ man hostname
[..]
THE FQDN
The FQDN (Fully Qualified Domain Name) of the system is the name
that the resolver(3) returns for the host name, such as, ursula.ex‐
ample.com. It is usually the hostname followed by the DNS domain
name (the part after the first dot). You can check the FQDN using
hostname --fqdn or the domain name using dnsdomainname.
You cannot change the FQDN with hostname or dnsdomainname.
The recommended method of setting the FQDN is to make the hostname
be an alias for the fully qualified name using /etc/hosts, DNS, or
NIS. For example, if the hostname was "ursula", one might have a
line in /etc/hosts which reads
127.0.1.1 ursula.example.com ursula
Better to just instruct embedded dnsmasq to not read the hosts file with below directive:
pi@ph5b:~ $ man dnsmasq
[..]
-h, --no-hosts
Don't read the hostnames in /etc/hosts.
EDIT: I have this one disabled enabled anyway bc we have local DNS records now
pi@ph5a:~ $ cat /etc/dnsmasq.d/99-no-hosts.conf
no-hosts
EDIT2: Ow and you most likely break sudo: