Need help to Ban IP

[Tonygoth]

Hi everyone, I'm a new user but read many of your topics of the forum. Since four months now, I've got a IP on my web that grab 30meg of bandwidth... that represent 25% of my using and it 1/500 visitor. I need to band this visitor IP. Last week, I discover that I could use .htaccess to ban it. Have got few questions to do so!

1) Don't know if I should ban it in cast that could be a good Bot. Here is the IP : 68-184-**-58.cpe.ga.ch*rt*r.com. Does anyone know this address? By the way, does someone have a complete list of spiders and bots that I should ban!

2) I try some script that I introduce inside my directory of my site. But always have a 500 code page. Could someone take a look and tell me if something wrong. I build this script with Word and change with my FTF program the .htaccess.txt to .htaccess. Her is my script:

order allow, deny
deny from 68.184.**.58
allow from all
RewriteEngine on
RewriteCond %{HTTP_REFERER}!^$
RewriteCond %{HTTP_REFERER}!^http://(www\.)?mydomain.com/.*$ [NC]
RewriteRule \.(gif¦jpg)$ - [F]

Thanks in advance! Tony

[edited by: jdMorgan at 5:15 pm (utc) on Nov. 26, 2004]
[edit reason] Formatting & obscured specifics per TOS. [/edit]

[jdMorgan]

Tony,

Welcome to WebmasterWorld!

A few things to check:

First, look at your server error log whenever you get an error. It will often tell you what is wrong.

Next, many server configurations will require you to add the line

 Options +FollowSymLinks 

before you can use mod_rewite

Lastly, it is a relatively common thing for the digit groups in reverse-DNS lookups to be reversed. So the actual IP *may* be 58.84.***.68. One way to check is to look up the IP address at arin.net to see which digit-group order resolves to the remote hostname you are seeing.

Major search engine robots will have their own registered IP block. This does not look like a legitimate search engine robot.

We have an enormous series of threads on 'bad bots' here. However, be warned that deciding whether a given robots is "good" or "bad" for *your* site is a subjective thing. What is a "good" 'bot for your site may be "bad" or useless for another site.

Another issue is that one can easily get carried away banning bad-bots. The list is huge, and will normally be processed for every single page, image, css file, and included JS file on your site. This can lead to performance problems on busy sites. It may be wise to select only a few bad-bots from the list and ban those -- the ones that actually visit your site and cause problems. Some of the 'bots in the list have been "retired" or have been dormant for a long time. You must make your own choices here; no-one else can give you one "right" answer.

Most recent thread (follow link in first post to see earlier parts 1-3): A Close to perfect .htaccess ban list - Part 4 [webmasterworld.com]

Jim

[Tonygoth]

Thank's jdMorgan,

I'll try this weekend and let you know if something wrong!

Before I go, I just want to know how could I
"look at my server error log to get the error. " I just ask at the live service of my server and they could inform me proprely for this issue. Could I get the server error log in a different way? Sorry if this question look easy but I'm a newbie and want to learn....

[jdMorgan]

Access to your server log depends on your host. It will appear in whatever directory they choose to put it in, and you will have to ask them where it is. If you cannot get your server error log data, change hosts; It is very difficult to develop and maintain a 'serious' Web site without basic services.

Jim

[Tonygoth]

I've got new,

Well, I took a look on my log error and I saw that all my bad log came from [someothersite.net...] I even dont know this web. So I believe that I been thief from my bandwith or I've been copy (page html) by a chiniess web. The log error show is [someothersite.net...] But when I go to this page it transfer me automaticaly at [example.com....] Does someone have a clue for this situation?

[edited by: jdMorgan at 12:52 am (utc) on Nov. 28, 2004]
[edit reason] Removed specifics. Please see TOS. [/edit]