Hi,
127.0.1.1 appeared again is a perpetual thread. I have another question,
so I decided to start a new thread.
unicorn:~$ grep unicorn /etc/hosts
127.0.1.1 unicorn.wooledge.org unicorn
This line makes various dnsmasq instances (they may be started by
lxc-net.service, for NetworkManager shared connections) giving 127.0.1.1
in response to queries.
Is it just a bug in dnsmasq that should filter out 127.x.y.z addresses
during reading of /etc/hosts or it is a reason to avoid 127.0.1.1 line?
My impression is that systemd-hostnamed(8) and hostnamectl(1) have been
created to address similar issues.
Previous time the topic was touched in
David Wright. Re: 127.0.1.1 line, was Re: chrome web browser worthless.
Fri, 4 Aug 2023 21:26:52 -0500.
https://lists.debian.org/msgid-search/zm2zber1h2el0...@axis.corp
with a link to
Christoph Anton Mitterer. /etc/hosts and resolving of the local
host/domainname - 127.0.0.1 vs. 127.0.1.1. Tue, 30 Jul 2013 22:43:44 +0200
https://lists.debian.org/msgid-search/1375217024.5442.102.ca...@fermat.scientia.net
