From: Pavel Volkov <negaipub@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Make BIND inject queries
Date: Tue, 23 Jul 2013 21:24:19 +0400 [thread overview]
Message-ID: <1998644.gJpNEbiNxq@melforce> (raw)
In-Reply-To: <51EE3E0F.1080302@gmail.com>
On Tuesday 23 July 2013 10:25:51 Alan McKinnon wrote:
> What you want to accomplish is cache-poisoning. There's a few ways to do
> it, but it's not easy.
>
> You can load the customized copy of the zone onto the cache that your
> internal hosts use, or set up an authoritative internal-only server.
>
> This stuff gets tricky, every time I have to investigate our setup that
> does something similar, I need to work it out in my head all over again.
>
> The best advice I can give is DO NOT TRY AND ACCOMPLISH THIS WITH ONE
> DNS AUTH SERVER THAT SERVES INTERNAL AND EXTERNAL CLIENT. That way lies
> a whole lotta pain.
I see. This is a trivial feature in Dnsmasq (that's where I got the idea
from), didn't except it to be this complicated in BIND.
prev parent reply other threads:[~2013-07-23 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 7:40 [gentoo-user] Make BIND inject queries Pavel Volkov
2013-07-23 7:45 ` staticsafe
2013-07-23 8:11 ` Pavel Volkov
2013-07-23 8:25 ` Alan McKinnon
2013-07-23 17:24 ` Pavel Volkov [this message]
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=1998644.gJpNEbiNxq@melforce \
--to=negaipub@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