1 |
Sorry this is unsolicited, but-- |
2 |
|
3 |
If anyone is looking for a solid, secure alternative to bind, check |
4 |
out nsd. It aims to be equivalent to bind on the wire, and reads bind |
5 |
zone files. There's an ebuild in bug 128246. I've been pretty happy |
6 |
with it for the last 6 months or so. |
7 |
|
8 |
http://www.nlnetlabs.nl/nsd/ |
9 |
|
10 |
If we can get some more people using it, maybe it'll finally be |
11 |
accepted into portage. |
12 |
|
13 |
Cheers, |
14 |
Peter |
15 |
|
16 |
On 9/6/07, kashani <kashani-list@××××××××.net> wrote: |
17 |
> Christian Parpart wrote: |
18 |
> > so, i googled around a bit, and found that the remote name server does not support/understand |
19 |
> > the incoming request, that is, resolving one of the above records to A (IPv4 address), |
20 |
> > which is kinda unbelievable. |
21 |
> > |
22 |
> > so how get i rid of these messages then? |
23 |
> > does anyone have a hint here? |
24 |
> |
25 |
> I like letting named handle its own logging and rotating. Here's post I |
26 |
> wrote on the forums showing the config I use for logging in Bind. It |
27 |
> helps keep shunt poorly configured server chatter into their own log |
28 |
> files leaving messages and general.log for important things. |
29 |
> |
30 |
> http://forums.gentoo.org/viewtopic-t-243393-highlight-named+general+kashani.html |
31 |
> |
32 |
> kashani |
33 |
> -- |
34 |
> gentoo-server@g.o mailing list |
35 |
> |
36 |
> |
37 |
-- |
38 |
gentoo-server@g.o mailing list |