[reSIProcate] RE: DNS blacklist
There will be two main ways to 'blacklist' a target. One is more to the end
of the list(discussed in earlier e-mails), the other will be to mark the
element as something that should be skipped for n seconds. We can certainly
expose that as an API the application can use.
--Derek
CONFIDENTIALITY NOTICE
This email and any files transmitted with it contains proprietary
information and, unless expressly stated otherwise, all contents and
attachments are confidential. This email is intended for the addressee(s)
only and access by anyone else is unauthorized. If you are not an addressee,
any disclosure, distribution, printing or copying of the contents of this
email or its attachments, or any action taken in reliance on it, is
unauthorized and may be unlawful. If you are not an addressee, please inform
the sender immediately and then delete this email and any copies of it.
Thank you for your co-operation.
> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@xxxxxxxxxxx]
> Sent: Monday, March 21, 2005 9:35 AM
> To: resiprocate
> Cc: Scott Godin; derek McDonald
> Subject: DNS blacklist
>
> In the DNS blacklist implementation currently being worked, I know
> we're dealing with sites we fail to reach. Does the current
> implementation
> also capture 503/Retry-After, and weight the node that came from
> appropriately?
> (I think I remember that being part of the first pass).
>
> Will there be an interface where the application can say "treat this
> location as if I had
> received a 503/Retry-After"?
>
> RjS