On Monday 13 July 2009 14:27:46 Karl Vogel wrote:
>It's very easy to set up a caching nameserver without using all the
>memory on your system.
It's much easier to turn your HIGH-performance webserver into a slug, by
running stuff you don't need on the same machine. Memory unused by the
Karl Vogel wrote:
On Jul 13, 2009, at 6:27 PM, Karl Vogel wrote:
K> You can fix the security problems by dumping Bind and using djbdns.
On Tue, 14 Jul 2009 10:16:24 +0200, Ruben de Groot replied:
R> What security problems? This one ? :)
R> http://blogs.zdnet.com/security/?p=2812
When BIND
>> On Jul 13, 2009, at 6:27 PM, Karl Vogel wrote:
K> You can fix the security problems by dumping Bind and using djbdns.
>> On Tue, 14 Jul 2009 10:16:24 +0200, Ruben de Groot replied:
R> What security problems? This one ? :)
R> http://blogs.zdnet.com/security/?p=2812
When BIND offers (and make
Steve Bertrand wrote:
>
> I like whatever works in regards to the situation I'm facing ;)
And that's the best possible reason one could have! ;-)
Peter
--
http://www.boosten.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
Peter Boosten wrote:
> Ruben de Groot wrote:
>> On Tue, Jul 14, 2009 at 12:46:43AM -0400, Steve Bertrand typed:
>>> John Almberg wrote:
On Jul 13, 2009, at 6:27 PM, Karl Vogel wrote:
>You can fix the security problems by dumping Bind and using djbdns.
>> What security problems? This on
Ruben de Groot wrote:
> On Tue, Jul 14, 2009 at 12:46:43AM -0400, Steve Bertrand typed:
>> John Almberg wrote:
>>> On Jul 13, 2009, at 6:27 PM, Karl Vogel wrote:
You can fix the security problems by dumping Bind and using djbdns.
>
> What security problems? This one ? :)
> http://blogs.zdn
On Tue, Jul 14, 2009 at 12:46:43AM -0400, Steve Bertrand typed:
> John Almberg wrote:
> > On Jul 13, 2009, at 6:27 PM, Karl Vogel wrote:
> >>
> >>You can fix the security problems by dumping Bind and using djbdns.
What security problems? This one ? :)
http://blogs.zdnet.com/security/?p=2812
>
Steve Bertrand wrote:
[...snip...]
> There is a single file in /etc/dnscache/root/ip, named 127.0.0.1
>
> If you want this cache to serve internal /24 network queries:
>
> % touch /etc/dnscache/root/ip/192.168.0
Need to add some clarification:
Adding the new empty file permits queries from th
John Almberg wrote:
>
> On Jul 13, 2009, at 6:27 PM, Karl Vogel wrote:
>
On Mon, 13 Jul 2009 13:03:24 -0400,
Jon Radel said:
>>
>> J> Apache and Bind have both had their security issues over the years,
>> and
>> J> there's something to be said for running them on different servers to
>
On Jul 13, 2009, at 6:27 PM, Karl Vogel wrote:
On Mon, 13 Jul 2009 13:03:24 -0400,
Jon Radel said:
J> Apache and Bind have both had their security issues over the
years, and
J> there's something to be said for running them on different
servers to
J> reduce both the "all eggs in one bask
>> On Mon, 13 Jul 2009 13:03:24 -0400,
>> Jon Radel said:
J> Apache and Bind have both had their security issues over the years, and
J> there's something to be said for running them on different servers to
J> reduce both the "all eggs in one basket" factor and the ease of
J> spreading an attack.
On Jul 13, 2009, at 3:05 PM, Mel Flynn wrote:
On Monday 13 July 2009 08:36:42 John Almberg wrote:
The other day, a FreeBSD 'expert' told me that it is important to
have the DNS server for a domain on the same server as the domain's
web server. Supposedly, this saves doing tons of DNS look ups
On Monday 13 July 2009 08:36:42 John Almberg wrote:
> The other day, a FreeBSD 'expert' told me that it is important to
> have the DNS server for a domain on the same server as the domain's
> web server. Supposedly, this saves doing tons of DNS look ups over
> the network. Instead, they are done lo
On Mon, Jul 13, 2009 at 12:36:42PM -0400, John Almberg wrote:
> The other day, a FreeBSD 'expert' told me that it is important to
> have the DNS server for a domain on the same server as the domain's
> web server. Supposedly, this saves doing tons of DNS look ups over
> the network. Instead,
On Jul 13, 2009, at 12:36 PM, John Almberg wrote:
The other day, a FreeBSD 'expert' told me that it is important to
have the DNS server for a domain on the same server as the domain's
web server. Supposedly, this saves doing tons of DNS look ups over
the network. Instead, they are done loc
John Almberg wrote:
The other day, a FreeBSD 'expert' told me that it is important to have
the DNS server for a domain on the same server as the domain's web
server. Supposedly, this saves doing tons of DNS look ups over the
network. Instead, they are done locally.
This makes sense to me, b
In response to John Almberg :
> The other day, a FreeBSD 'expert' told me that it is important to
> have the DNS server for a domain on the same server as the domain's
> web server. Supposedly, this saves doing tons of DNS look ups over
> the network. Instead, they are done locally.
>
> Thi
The other day, a FreeBSD 'expert' told me that it is important to
have the DNS server for a domain on the same server as the domain's
web server. Supposedly, this saves doing tons of DNS look ups over
the network. Instead, they are done locally.
This makes sense to me, but I wonder if the p
18 matches
Mail list logo