Cannabis.com hosted by Rackspace.com?

I've been having some problems with my ip blocker, it's been blocking cannabis.com and rackspace.com marking it "fake emule server" each time I try to connect to cannabis.com, (leading me to believe that maybe a fake emule server and cannabis.com are both hosted on rackspace, but I dont know much about all that networking stuff.) so i looked up the ip address its blocking with whois and found that it falls within the range of... well hell, i'll just copy the results.

Here they are:

Quote:

---

Rackspace.com RSPC-NET-2 (NET-209-61-128-0-1)
209.61.128.0 - 209.61.191.255
MoreVisibility.com RSPC-4228-1008183192 (NET-209-61-129-128-1)
209.61.129.128 - 209.61.129.159

# ARIN WHOIS database, last updated 2005-07-11 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.

---

I just want to make sure this is who I'm supposed to be connecting to before I tell my ip blocker to allow the connection.

I'd be thankful for any feedback.

That's the same information returned by my traceroute software, so I'd say it's accurate. You should be able to plug in the site's IP address (69.20.47.163) into your firewall's whitelist, which should stop the problem.

Alright, thanks for the help.

I'm not that familiar with emule (a file trading program I presume), so I'm not sure what to suggest ... with that said, does the filter indicate exactly what IP address(es) are being blocked - that would be more helpful than an IP range, which can be quite large...

Note the ARIN information that mentions MoreVisibility.com is out of date - they appear to have been delegated the IP range (a portion of which we are now in) at one time in the past; they're still hosted with RackSpace elsewhere.

Be aware tracert has numerous limitations ... one of which is most tracert programs will resolve only one IP (often at random) for the domain entered regardless of how many IPs are associated with the particular domain ... cannabis.com homepage is mirrored, so you'll need need to put in 209.61.129.146 into your whitelist too - also the boards here are on 69.20.47.161 and thus should be added as well.

IPs are subject to change at any time so IP whitelists/blocklists need to be reviewed regularly for changes.

Ron

Thanks Ron, that cleared it up. It was blocking 209.61.129.146, but only because that ip fell within the same range as some fake emule server/servers that were blacklisted.