On Mon, 25.01.16 09:08, Florian Weimer (fweimer@xxxxxxxxxx) wrote: > > It is intended as a convenient fallback mechanism, and is only supposed > > to have an effect if 'gateway' is not defined in the local DNS (the > > 'domain' or 'search' zones). Would it help if those limitations were > > more explicit, e.g. documented in nss-myhostname(8)? > > I understand that the goal is that nss_myhostname will not override > existing names, due to the way the NSS is configured. > > What I do not understand is how the the “gateway” name can be > useful. Here's a very obvious, trivial example: wherever I am I can now simply type "ping gateway" to know whether connectivity to my local router works. I also know that in my local wlan, as well as in the one of my girlfriend's or my parent's: I can reconfigure the router by typing http://gateway/ into my webbrowser, without having to check IP configuration, leave the web browser, or even know the router's brand or default configuration. > As I tried to explain above, I'm not really worried about nss_myhostname > overriding name resolution, but that software relies on the specific > functionality of the “gateway” name provided by nss_myhostname, but > *this* name is overridden by DNS (with a suitable search path) or > nss_files, so that it no longer resolves to the expected address. Search lists are local configuration. Software which relies on specific search paths to be configured will already break pretty much everywhere... Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
