< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index | Next in Thread > |
Before the recent changes, that way I understood it the
blacklisting was supposed to work as follows: 1.
Only blacklist an entry if there other DNS entries to try. 2.
If we have ended up blacklisting all entries from a particular lookup,
then un-blacklist them all and let the next request start the cycle again. Scott From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Byron
Campen This is
happening because the stack is blacklisting the tuple that your server was
running on, because it didn't respond. This blacklist (currently) lasts 32s. I
was thinking about making this duration configurable. Does anyone want to have
a discussion about whether blacklisting on a UDP timeout is something we want
to be doing? It seems to me that we might need to have a concept of
"greylisting", where greylisted tuples will only be used if they are
all that remains to be tried. (This is opposed to a blacklisted tuple, which we
should never try, since chances are we have been explicitly told, with a 503,
to leave the tuple alone for a while.) Any thoughts? (anyone?) Best regards, Byron Campen
|