[db-wg] Modifying the ACL for the whois server
- Previous message (by thread): [db-wg] Modifying the ACL for the whois server
- Next message (by thread): [db-wg] ANNOUNCEMENT: "auth:" Attribute is Now Searchable
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Engin Gunduz
engin at ripe.net
Mon Jun 7 12:10:46 CEST 2004
Dear Marwan, To unblock an IP, you need to connect to the configuration port, telnet whois_server config_port and =0= whois R.I.P. config> set acl <IP> deny=0 =0= whois R.I.P. config> set nodeny <IP> To provide unlimited access for an IP: =0= whois R.I.P. config> set acl <IP> maxprivate=-1 If you have any more questions, please don't hesitate to contact <ripe-dbm at ripe.net> or <db-help at ripe.net>. Regards, Engin Gunduz ____________________________ RIPE Database Administration. On 2004-06-06 07:16:28 +0400, Marwan El-Sherif wrote: > Dear Group, > > > The whois server has a very good feature implemented in it that > protects it from any form of abuse by enforcing ACL points. Now > because most of our staff are not very familiar with the CLI whois > client, we decided to go for a web interface for querying the whois > server. So we ran into the problem of the web server's IP being > blacklisted. I looked around the configuration of the ACL but could > not find any way to exclude such IPs from the `ACL points' system. We > already have the proper protection from any abuse on the web server. > We are running the RIPE Whois server 3.0.2. Is there any way to > exclude certain IPs from being blacklisted? > > > Regards, > > Marwan El-Sherif
- Previous message (by thread): [db-wg] Modifying the ACL for the whois server
- Next message (by thread): [db-wg] ANNOUNCEMENT: "auth:" Attribute is Now Searchable
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]