| To: | dns@list.cr.yp.to |
|---|---|
| Subject: | Re: peventing dns cache from answering queries |
| From: | Jeremy Kitchen <kitchen@scriptkitchen.com> |
| Date: | Tue, 5 Jun 2007 17:20:54 -0400 |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-djbdns@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list dns@list.cr.yp.to |
| In-reply-to: | <34297.200.131.233.134.1181071224.squirrel@quimera.cpd.ufv.br> |
| Mail-followup-to: | dns@list.cr.yp.to |
| Mailing-list: | contact dns-help@list.cr.yp.to; run by ezmlm |
| References: | <34297.200.131.233.134.1181071224.squirrel@quimera.cpd.ufv.br> |
| User-agent: | Mutt/1.5.13 (2006-08-11) |
On Tue, Jun 05, 2007 at 04:20:24PM -0300, gustavo.rios@ufv.br wrote:
> Dear gentleman,
>
> is there any way i could prevent dnscache from answering queries for
> domain xxxxx.zzz.yy and instead set it to tell the client to do it
> itself on address a.b.c.d ?
no.
and most clients would wonder what you're asking them to do, as it's
YOUR job to resolve the domain for them, not theirs.
However, what you can do is tell dnscache to use a.b.c.d to look up
domain xxxxx.zzz.yy (note that you should be using example.{com,net,org}
for examples per RFC2606) and that should do what it is I think you're
asking.
-Jeremy
--
Jeremy Kitchen ++ kitchen@scriptkitchen.com
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | peventing dns cache from answering queries, gustavo . rios |
|---|---|
| Next by Date: | Re: peventing dns cache from answering queries, Dean Anderson |
| Previous by Thread: | Re: peventing dns cache from answering queries, Dean Anderson |
| Next by Thread: | redirecting time service, Chris Smith |
| Indexes: | [Date] [Thread] [Top] [All Lists] |