Philippe Houdoin wrote:
/etc/networks is not often needed for... well, I don't even know what's his purpose!
resolv.conf is just a configuration file for the stub resolver. In effect it "supports" both static and dynamic entries with the lookup statement, ie lookup file bind. I dont see how it hurts to keep this file around since the stub resolver has to get it's configuration from somewhere.What is left is only resolv.conf. We should at some point replace it with a kernel DNS handler (which could support temporary and static DNS entries, I wrote this too often).
But we'll have still to support persistence of the static DNS entries after a reboot. Resolv.conf can be supported like others files in fact, except that instead of static arrays of default databases values, it should be a dynamic list of DNS entries.
I think you might have resolv.conf confused with the hosts file here.
But I've fear about it. Do you guys know about good/better opensource (and compatible with Haiku licence) DNS resolver than BIND's one?
skadns, BSD-like license http://www.skarnet.org/software/skadns/index.html
djbdns' library interface, Public Domain (afaik) http://cr.yp.to/djbdns/dns.html
--- Lars Hansson