Ok, after thinking about it more then at least some of this doesn't sound like it's DNS related.
Quote:
Originally Posted by NWLB.net
A user in France reports a "Forbidden" You don't have permission to access /rcifan01 on this server. Additionally, a 404 Not Found Error was encountered while trying to use an ErrorDocument to handle the request.
|
Does rcifan01 mean anything to you - i.e. is that a path which exists on your server, and/or have you recently changed the nameservers/server for your domain, where that rcifan01 path existed on the old server perhaps?
Quote:
Originally Posted by NWLB.net
Another user in the UK mailed her ISP. She's not a techie. In her words:
"Bad news. It's happened again! I went to it after you'd approved my membership to the forum and got that forbidden message. So I checked the DNS server numbers (which my ISP had given me) and it isn't working. I'm going to email them again."
She could see it at one point, signed-up, was approved by me, and saw it shortly afterwards. Now she can't access it again.
|
This bit does sound like it's perhaps DNS related - but if she's getting 403 forbidden she's obviously resolving the domain to something...
Quote:
Originally Posted by NWLB.net
The site is hosted in a subdomain of Cruiseaficionados.com.
|
Can these users who are having problems access this domain but not the other? Or are both affected?
Ruling out DNS is fairly easy. Get them to open up a command prompt and type:
Code:
nslookup www.royalcaribbeanfan.com
(followed by enter)
They should see something like:
Quote:
Server: resolver1.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: royalcaribbeanfan.com
Address: 69.73.139.20
Aliases: www.royalcaribbeanfan.com
|
The first bit isn't of interest so much - it's just about the DNS server they're using (in my case, opendns). The last part is what you're interested in - you should basically make sure that everyone gets the same IP address as that.
If someone gets a different IP, or some error message saying "non-existant domain" or similar then you know that DNS is the problem.
The other thing to check here is that since people are reporting 403 error messages, what is reported in your error_log on the server? If they're hitting the correct server, you should see a fair few 403 errors and that might shed some more light on what's going on.
__________________
Please login or register to view this content. Registration is FREE :: DDS & Dedicated, UK & USA-based Please login or register to view this content. Registration is FREE, Reseller & Shared Hosting
Experienced Parallels Platinum Partners (Plesk since 2001, Virtuozzo since 2003)
Last edited by damien_ls; 11-08-2007 at 12:03 PM..
Reason: fix typo
|