From: Tom H <tomh0665@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] resolving names of local hosts locally
Date: Wed, 16 Dec 2015 10:09:39 +0100 [thread overview]
Message-ID: <CAOdo=SyLVqBRYNGLfu0_dxozxFzDMnTjizrNT9H3w2zQ+oq=Xw@mail.gmail.com> (raw)
In-Reply-To: <CAC=wYCGaDpJfKB8QuDTeYO7=c7fQZrrjZ=-9eqfsw-M4CopMnw@mail.gmail.com>
On Wed, Dec 16, 2015 at 4:01 AM, Adam Carter <adamcarter3@gmail.com> wrote:
>>
>> There are several problems with your idea. First, the configured
>>
>> namservers in resolv.conf are caching servers, not authoritative
>> servers. You never configure an auth server to act as a cache. Yes, it
>> can be done. No, it's an awful idea and things break horribly.
>
> What breaks if you have caching and auth on the same server? I have been
> running my tiny home network this way for years. The local domain is
> properly delegated, but if you just wont a local domain that's not
> necessary.
The ISC recommends separating authoritative and caching bind servers.
The main reason that I can think of is that someone can poison the
cache of the domains for which a server's authoritative.
next prev parent reply other threads:[~2015-12-16 9:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 19:37 [gentoo-user] resolving names of local hosts locally lee
2015-12-02 19:52 ` Alan McKinnon
2015-12-02 20:11 ` Mike Gilbert
2015-12-03 22:20 ` lee
2015-12-03 22:39 ` Alec Ten Harmsel
2015-12-03 23:46 ` waltdnes
2015-12-16 3:01 ` Adam Carter
2015-12-16 8:41 ` Alan McKinnon
2015-12-16 9:09 ` Tom H [this message]
2015-12-16 9:26 ` Alan McKinnon
2015-12-16 12:52 ` Rich Freeman
2015-12-16 16:33 ` Alan McKinnon
2015-12-16 19:04 ` Tom H
2015-12-03 8:44 ` Peter Humphrey
2015-12-03 22:01 ` lee
2015-12-04 10:19 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOdo=SyLVqBRYNGLfu0_dxozxFzDMnTjizrNT9H3w2zQ+oq=Xw@mail.gmail.com' \
--to=tomh0665@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox