Date: Thu, 8 Mar 2001 23:08:54 -0800 From: "Crist J. Clark" <cjclark@reflexnet.net> To: David Preece <davep@afterswish.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: dhcpd and naming (warning, ranty). Message-ID: <20010308230854.V1367@cjc-desktop.users.reflexcom.com> In-Reply-To: <5.0.2.1.1.20010309165732.026f1fa8@pop3.paradise.net.nz>; from davep@afterswish.com on Fri, Mar 09, 2001 at 05:38:07PM %2B1300 References: <5.0.2.1.1.20010309165732.026f1fa8@pop3.paradise.net.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 09, 2001 at 05:38:07PM +1300, David Preece wrote: [snip] > God, I have to get bind going to be > able to resolve names for machines that are next to each other? BIND?? > There are whole books on bind. People go on training courses for it. It's > the #1 posessor of security holes, I don't want that running - I like to sleep. [snip] > Ah, fuckit. I have to hand one to the Windows weenies - here we have > another task that is just too difficult to be even remotely pratical on > Unix: naming on a Lan. Too depressing for words. Knowing just a little about how Win* name resolution works, I find the idea of worrying about BIND security holes kind of funny. Other than that, yes, name resolution is a bitch. (period) Doing name resolution on an IP network is pretty much always going to be kludgy since the concept of names does not exist in the IP itself. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010308230854.V1367>