https://bugzilla.novell.com/show_bug.cgi?id=383336
User mmeeks@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=383336#c34
--- Comment #34 from Michael Meeks 2008-05-06 03:16:04 MST ---
So - here is my personal summary:
Yast [ or affiliated system thingits ] needs (somehow) to assign a host-name to
the system.
Yast+ (or whoever made the boot CD or whatever) makes up an invalid hostname,
something like "linux.site"
Applications that trust the 'hostname' and try to hand it out elsewhere break,
and all the (very many) places that do a lookup on that hostname also time-out
taking a vast time to do so.
Apparently this is the rest-of-the-world's-fault for not knowing that that the
10 machines with hostname "linux.site" on that network should immediately
either fail to resolve, or magically somehow resolve to their own IP address ?
Should we suggest to router/DNS manufacturers to be hard-coding "linux.site",
or "*.site" as a magic domain-name to resolve to the requester's IP ? what
about when that request is proxied ? honestly - I find the concept that the
problem is "out there" rather than in our own network setup *extremely*
difficult to swallow.
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 ?
--
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.