system/settings/network/hosts missing resulting in non-resolving localhost

[waddlesplash]

NetResolv assumes that "localhost" actually exists, but in some instances it doesn't (it can't be resolved -- 127.0.0.1 exists, though).

This could be part of the issue with our DHCP issues in #12208, however it isn't the sole reason as adding a localhost line to hosts doesn't fix the DHCP issue.

[waddlesplash]

Strike that. In some instances, localhost isn't even created at all -- it doesn't exist on my system (!)

[axeld]

I might be dumb, but netresolv should be the one to provide "localhost" in the first place, no? It's the only name resolution entity out there (in Haiku) after all.

How about reverting the netresolv change, and go with FreeBSD's solution next time?

[pulkomandy]

localhost and the loopback interface are working fine here, without the need for an "hosts" file.

[kallisti5]

(In #12364) This looks like a duplicate of #12260... I need to confirm #12260 is still an issue though.

[kallisti5]

I did some digging, netresolv does provide localhost... by parsing the /etc/hosts like on most platforms :-). There could be edge cases of users wanting to modify where localhost points so setting it in a static way is really not ideal. As all the platforms I know of define localhost in some etc-hosts way, i'm going that route.

Fix on it's way.

[axeld]

As with the services, I could imagine that I hard-coded that into the former libbind solution in case there was no /etc/hosts file. It would probably make sense to look into that.

[kallisti5]

that's fair. #12368 was opened to track.

[kallisti5]

resolved in hrev49626