Date: Sun, 14 Sep 1997 21:40:03 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: Greg Lehey <grog@lemis.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Why not DNS (was: nfs startup - perhaps it is a problem) Message-ID: <199709150340.VAA21991@rocky.mt.sri.com> In-Reply-To: <19970915114213.54969@lemis.com> References: <199709142148.OAA22603@usr09.primenet.com> <199709150141.CAA26286@awfulhak.demon.co.uk> <19970915114213.54969@lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lehey writes: > If anybody can give me any reasons for using /etc/hosts, I'm sure I > can refute them. - The box *IS* the primary DNS box for my network, and hence can't resolve addresses at bootup until after DNS is running, but needs some resolution in other parts of the system for starting up things until DNS gets running. - The box is on a private home network made up of two hosts, and these machines need to talk to each other at times. Setting up a DNS server is a waste of resources for a private network. - The machine in question is using a slow and/or part-time network connection, and while doing 'local' work with sockets and such (programming, etc...) doesn't need to have the link up, and/or doesn't need to be using bandwidth usable for other processes. Could I run DNS and solve some of my problems? Of course, but it'd be like hammering nails with a sledge-hammer. It gets the job done, but it's way overkill. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709150340.VAA21991>