Hi, I just set up this new forum account because I am not sure if what I am seeing in this new IP Fire install I did recently is a problem. I set the domain to use home.arpa per RFC8375 RFC 8375: Special-Use Domain 'home.arpa.'
So IP Fire shows ipfire.home.arpa and hostname shows localhost.home.arpa, ok, good. But, when I login to IP Fire using ssh, and ping localhost in the terminal, IP Fire responds “64 bytes from localhost.localdomain (127.0.0.1)”. I looked up how to edit hosts file under /etc, and changed that from “127.0.0.1 localhost.localdomain localhost” to “127.0.0.1 localhost.home.arpa localhost”, saved the file, and rebooted IP Fire. After IP Fire restarts, I login to it, and run “ping localhost” in the terminal again, and the response is “64 bytes from localhost.localdomain (127.0.0.1)”. I searched around on Google, and see this is kind of a common issue with Linux distros. One of the solutions I tried was adding “kernel.hostname = localhost.home.arpa” to sysctl.conf, saving that file, doing sysctl -p in the IP Fire terminal, rebooting the system, and once again pinging “localhost” in a terminal brings back the same host name “localhost.localdomain”. So I’m not sure, it seems IP Fire is using the “home.arpa” domain, and the DNS and networking seems to work fine, but, I think this is kind of strange, that the IP Fire admin page shows “localhost.home.arpa” and yet in the system terminal IP Fire seems to think it is localhost on localdomain. Any advice, or suggestions how to get these to parity, so they do not contradict each other? Or is this a nothing burger. I have a PC and networking background, and education, and from what I remember, I cannot see this kind of disparity in the localhost FQDN not matching the Domain information for the system working well, or not causing connection or security issues in the long run. Thanks -HR
hello Hanlon - Welcome to the IPFire Community!
This is a little hard to follow. Images / screenshots will help!
Is this the screen that you set domain to home.arpa??
If not, where was it set to home.arpa??
I think this should be just home (and not home.arpa).
Still trying to learn the forum, I posted some replies but uh, oops, deleted by accident.
Yeah Jon, if you set that to home.arpa it looks like this in IP Fire here:
pfSense was talking about this about two years after IETF made the change allowing home.arpa to be used in residential homes Todo #10533: Change default domain for new installations from "localdomain" to "home.arpa" - pfSense - pfSense bugtracker
I still cannot figure out what is overwriting /etc/hosts each time I start IP Fire so localhost is defined as:
127.0.0.1 localhost.localdomain localhost
I just edit the /etc/hosts file each time I start IP Fire and change that to read:
127.0.0.1 localhost localhost
and IP Fire is good for the day. Ping responses in the IP Fire terminal for localhost come back:
[root@ipfire ~]# ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.049 ms
after I make the edit and save it to /etc/hosts
Gets kind of tiresome to have to make that edit each time I start IP Fire. Sure would like to know what is set to write /etc/hosts to read ‘localhost.localdomain’ and fix that. Oh well.
@jon gives you the right hint, to change the domain for the red LAN you must do the
setup
command again and change this domain here, this works permanently.
One more time to remember the basic processing in IPFire.
The config is hold (mostly) in IPFire’s own settings files. The system generates the configurations of the Linux processes from this. Local modifications should be set in the associated .conf.local files, if available.
I didn’t look at this special system setting, but I suppose conservatively the system domain is pulled from the IPFire config at startup. This means also, that the domain is valid not before a restart.