From: Alex Efros <powerman@powerman.name>
To: supervision@list.skarnet.org
Subject: Re: dnscache endless resolving loop
Date: Thu, 28 Feb 2008 18:21:48 +0200 [thread overview]
Message-ID: <20080228162148.GB27827@home.power> (raw)
In-Reply-To: <Pine.LNX.4.64.0802281101360.10775@e-smith.charlieb.ott.istop.com>
Hi!
On Thu, Feb 28, 2008 at 11:16:45AM -0500, Charlie Brady wrote:
>> server")... dnscache run on 127.0.0.1 so it isn't remote attack.
>>
>> After all I got an Idea: maybe it's dnscache is the one who asking
>> dnscache? :) I did strace, and, yes, it looks like dnscache send PTR
>> requests to itself in endless loop.
>
> Move your dnscache to, say, 127.0.0.9, and you will escape this loop.
> Or add an override delegation for that reverse zone, in ./root/servers.
... and repeat this each time something like this happens? :(
Actually, all of this in fact is remote DoS attack (but not intentional,
of course) to dnscache running on 127.0.0.1. WOW! :)
--
WBR, Alex.
prev parent reply other threads:[~2008-02-28 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 15:22 Alex Efros
2008-02-28 15:38 ` Jose Celestino
2008-02-28 16:30 ` Alex Efros
2008-02-28 16:16 ` Charlie Brady
2008-02-28 16:21 ` Alex Efros [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=20080228162148.GB27827@home.power \
--to=powerman@powerman.name \
--cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).