Expected Behaviour: Pi-Hole using "debianserver" as the hostname; this was set in the Debian 11 installation and works, when Pi-Hole is NOT used as a DNS Server. Actual Behaviour: The moment when I set my Pi-Hole Machine (a older laptop which runs a lot of services) as the DNS Server in the FRITZ!B…

[image] PhilIsHere: I showed that my /etc/host is indeed empty in my initial Post That file is different from /etc/hosts - note the trailing s. :wink: Please try removing that 127.0.1.1 line as suggested. You'd then have to restart Pi-hole's DNS resolver, e.g. by running pihole restartdns. …

[image] PhilIsHere: Pi-Hole automatically assigns pi.hole as the hostname. The original hostname still works and still applies. Pi-hole adds pi.hole as a consistent internal hostname for its own operations.

[image] chrislph: The original hostname still works and still applies Well. No it does not because it returns the localhost adress which breaks everything. I assume it's the IP Adress of the Loopback Adapter, which is for whatever reason returned. I did however selected eno0 (my LAN Interfac…

[image] PhilIsHere: it returns the localhost adress That's not a Pi-hole artifact, this would also be the case if you were pinging the hostname of the localhost before you installed Pi-hole. It's configured in /etc/hosts. Eg some Linux setups here all resolve the hostname to 127.0.1.1: pi@pi…

One can clearly see that fe80::REDACTED:REDACTED:REDACTED:REDACTED%20 is a correct IP address of your Pi-hole host machine. Compared to that, an incorrect IP address would of course be something like fe80::REDACTED:REDACTED:REDACTED:REDACTED%20, whereas fe80::REDACTED:REDACTED:REDACTED:REDACTED%20 o…

[image] chrislph: It's configured in /etc/hosts. Eg some Linux setups here all resolve the hostname to 127.0.1.1: [image] Bucking_Horn: As for your naming issue: The debian installer creates an entry associating 127.0.1.1 with your hostname in /etc/hosts (see Debian's docs at 5.1.1. The …

[image] Bucking_Horn: That file is different from /etc/hosts - note the trailing s. :wink: Oh my god... It works now thank you!!

[image] Bucking_Horn: If you are not running software on that host machine that may depend on that value, you may safely remove that 127.0.1.1 debianserver line from your /etc/hosts. (This should usually be the case for headless server installations) Am not sure if thats recommended. That w…

I've removed it in the past and it did impact sudo, which gave an error every time it was invoked, so I put it back. I believe the order of resolution is controlled in /etc/nsswitch.conf (the hosts line) but I'm not sure if that is still relevant in modern Debian-based OSs. I've never needed to tou…

This is what I always do for systems with static IP details like Pi-hole: [image] Sudo: unable to resolve host {hostname}: Name or service not known Help Figure out your hostname: pi@ph5b:~ $ hostname ph5b Figure out your DNS search/suffix domain: pi@ph5b:~…

[image] deHakkelaar: 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. Local processes could also make use of /etc/hostname to retrieve the hostname. Associating 127.0.1.1 with …

Pihole overrides hostname without being instructed to do so

Help

deHakkelaar June 15, 2023, 7:57pm 12

This is what I always do for systems with static IP details like Pi-hole:

EDIT: Ow you could do an extra:

pi@ph5b:~ $ hostname -i
127.0.1.1

pi@ph5b:~ $ hostname -I
10.0.0.4