https://bugzilla.novell.com/show_bug.cgi?id=383336
User lnussel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=383336#c36
--- Comment #36 from Ludwig Nussel
Why should we assign a host-name/domain that is known to be invalid & then not resolve it ourselves quickly locally & expect other people to be able to do that ?
The host name is not really invalid. It's just not resolvable in the global DNS. The solution is not trying to resolve it. If an applications wants to find out about the system's IP addresses (plural) it should use getifaddrs() instead of gethostbyname(). Note that gethostbyname() always returns the wrong IP for unassigned names, either it times out or returns 127.0.0.2, both doesn't have the desired effect. Having said that we shouldn't use linux.site as host name indeed IMO. $RANDOM.local would be better as .local is catched by nss_mdns and shouldn't be looked up globally and can be resolved in the LAN for ad-hoc networks (provided the firewall is configured properly of course :-). I fear that there are other timeouts involved in that case though. avahi could probably take the shortcut and resolve the local hostname instantly to all ip addresses. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.