yes im sure... i checked that out, it was the first thing i did.. the only way i knew was i had the Multiple account login detector (AE Detector) installed...

DementedMindz: Where is your website located at? I can try and take a look at it.

In other news, I made some modifications and this hack is now at version 1.0.4. New features include:
1) Being able to use wildcards in allowed IP addresses, i.e. 192.168.0.*
2) Being able to allow hosts from REMOTE_HOST, i.e. *.aol.com.

Keep in mind that the allowed hosts bit only works if your server does the reverse DNS lookups for REMOTE_HOST from REMOTE_ADDR. That's easily verifiable with a phpinfo script.

see its strange it stops me when i try but a few users who didnt come back for a few days were able to make new names... and they had same ip..

Really, I mean it. If you tell me where your website is, I can try for myself :p Honestly, I would guess that it's because their IP actually did change over the course of a couple days, but yet the notify plugin that you mentioned is notifying you because that checks for Post IPs also. If you would enable post IP bans with this plugin, it would prevent those from happening... though it might also prevent certain people from registering who you want to register.

i looked at there ip its the same ip number its a cable static ip address.... also that hack Multiple account login detector (AE Detector) dont check for there ip its cookie based...

is there any way you could make a feature (with on/off feature in admincp) that is cookie based also like the Multiple account login detector (AE Detector) this way it would auto ban them or stop them???

I might do that some other time, but at this point it's not something I'm especially interested in. The reason is that anyone could simply clear their cookies and reregister, and I'm not interested in making a block that's that easily bypassable.

it seems to work great on Multiple account login detector as it dont use the default vbulletin cookie... this way if they log out it wont clear that cookie...

Did you test your newest version on the wildcards?

thank ，
Installed without a hitch !

I did, as much as I was able. I was slightly limited by my server's abilities and not able to test everything 100% thoroughly, but everything that I was able to test worked correctly. Why, did you have a problem?

I am using *.aol.com as a wildcard. I have tested this on an AOL dialup account, and it has given me the message of "Our system shows that you have already registered under a different name".

I am receiving many emails from users from AOL not being able to signup.

any ideas?

1) Are you sure your server resolves hostnames? I'd recommend making a phpinfo script and checking.
2) Are you sure that the hostname actually ends in .aol.com?

1) I can access my phpinfo file. What am I looking for? I searched the page for "resolve" or "hostnames"...not much came up. Do you have that script or know where to get it to find out?

2) *aol.com or .aol.com? I see you put .aol.com

1) Look for a variable called "REMOTE_HOST"... it should be under the "Environment" section, probably next to "REMOTE_ADDR."
2) Either one should work, but *aol.com might allow unlimited registrations from someone coming from a host like maol.com :p

Also, could you go to this website with the AOL connection and let me know what it says that the hostname is?

Krofh, check your PMs

Updated to 1.0.5... the "Allowed Hostnames" bit only worked with hosts resolving REMOTE_HOST, and it seems that wasn't an option enabled by default in Apache. Now it resolves hostnames independently through PHP from REMOTE_ADDR.

updated mine!

Is the hostname bit working for you now?

Ahh... Sorry about that, I spose that's just the risk with this sort of a hack.

Does this work with 3.6.x?