From: Toens Bueker (toens.buekergmx.net)
Date: Wed Sep 17 2003 - 14:58:53 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

John Peach <postfixjohnpeach.com> wrote:

>> what stops you from running tinydns somewhere in 127/8? or do you
>> run an operating system that can't assign more than one IP to an
>> interface?
>
> I'm very wary of tinydns anyway. By "design" it doesn't
> answer TCP queries, which, of course, breaks recent
> billyshit impementations which only speak TCP. It does not
> appear to be well documented how tinydns for an *internal*
> only nameserver can interact with dnscache for the rest of
> it.

http://www.fefe.de/djbdns/#splithorizon will help you.

> Obviously I cannot tell the root nameservers that I am
> authoritative for doubleclick.net et al and I use this
> nameserver for my home network.

You won't have to.

> BIND has been doing a perfectly acceptable job for me
> and with the patched version(s) released this morning, I
> prefer the way that the ISC have solved the problem to the
> patch for dnscache which relies on hardwiring the IP
> addresses returned.

It's pretty straightforward, though.

by
Töns
--
There is no safe distance.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]