Re: DNSBL mirror inquiry
Alica CCS <[email protected]> Sat, 11 Jun 2005 16:28:36 +0800 (CST)
| Newsgroups | gmane.mail.spam.dsbl.general |
|---|---|
| Message-ID | <[email protected]> |
The server located at 163.25.104.5 once worked in April, but in May the server's network session load grew to a level that our NAT equitment cannot sustain. Because we have more computers than our ips, we need to maintain a NAT block which covers our whole campus, including about 30 class C public ip blocks and about 100 class C private ip blocks. The situation is the person who manages our outbound connection and NAT devices insisted that the sessions should below the alarm level of NAT, or he will block all DNS query sessions to 163.25.104.5 and reserve sessions for ordinary use. Surely our service cannot affect the whole campus, and we didn't find any measure to rate limit the sessions to our server. The server is still running, but massive requests to it made it unaccessible from outside network--- it's a pity that we cannot sustain the load. Do you have any idea to rate limit the queries? If not, then we have no other choices but only resign to be a official DSBL mirror. Sorry for the inconveniences. Chih-Shun Chen CCCC, Chang-Gung University On Thu, 9 Jun 2005, Michael Tokarev wrote: > Alica CCS wrote at Fri, 15 Apr 2005 17:35:43 +0800 (CST): > >> Hi all, we are interested in providing public DNSBL mirrors in Taiwan. [..] > > It was quite some time ago, and we haven't heard anything > back (or did I miss the conversation?) > > The server you've set up is listed on http://dsbl.org/nsstatus page, > but it times out (does not answer any queries) for some two months > now -- is it ok? > > (While it is listed on the nsstatus page, it is NOT put into > main list of dsbl.org nameservers - we wanted to ensure it is > working as expected, but it does not work at all...) > > /mjt ---------------------------------------------- This message was sent to the opt-in DSBL list. If you do not want to receive DSBL messages, please send mail to [email protected].