On Mon, 2004-08-23 at 21:51 +0800, John Summerfield wrote: [...] > Then it's the user's task to configure the system appropriately. I run a > webserver. I can configure it to listen to any IP address I choose, > including 127.0.0.1. I don't need any bogus network interfaces, IP > addresses or host names misconfigure by the vendor. > > I mentioned _those_ programs by name because they were mentioned in the > email that attracted my attention. None of those require a > (misconfigured) hostname to resolve to anything. > > Better to allow the user to configure the system _properly_ and to have > it fail if it's broken than to make it work with misconfiguration. Are we forgetting the premise on which name resolution was developed? First successful query wins. For machine that are connected to the Internet but on multiple networks that may or may not have Internet service... nsswitch.conf For successful Network Init: hosts: dns files For unsuccessful Network init: hosts: files dns This single change would take care of 99% of the problems. Make an option during setup, if this machine is a "multiple" config machine, then let this get changed... you could also manage resolv.conf this way as well. Be nearly transparent. There are other ways you could do this. Maybe I am not really looking this through properly. But I doubt that. DHCP and DNS need to be coordinated properly, though. -- greg, greg@gregfolkert.net The technology that is Stronger, better, faster: Linux
Attachment:
signature.asc
Description: This is a digitally signed message part