Domain Problems
June 23, 2006 9:31 AM   Subscribe

We are having a very strange issue with our domain when accessed from our offices here, and we've run out of troubleshooting ideas.

As a little background info - we have this problem domain hosted on a server with a dozen or so others, that have no problem.

Here are the symptoms:

- Unable to access HTML or PHP files on our domain from this office (using our local cable internet access).

- PHP and HTML files on our domain load fine from all other ISPs and locations we have tested.

- Image files and text files on our domain load fine.

- The same PHP and HTML files uploaded to another domain on the same server as our domain work fine.

We've tried rebooting the server to no avail and our ISP swears up and down its not them. They've made the suggestion that its the firewall on our server, but I just don't see how it could be the case.
posted by finitejest to Technology (8 answers total)
 
Are your office computers hostnames using the same domain? If so it could be a problem with DNS getting confused. If your office computers are on a private network and then try to access your webserver that is seperate of your private network it is very easy to get confused.

Another thing is it could be the webserver configuration.
posted by dyno04 at 10:06 AM on June 23, 2006


confused how? We are all on a network if that helps

And as far as I know the server config has not been changed.

Also, I switched us all to a free proxy server, which seems to work fine.
posted by finitejest at 10:11 AM on June 23, 2006


Is the server in question on the same network as you guys?
posted by ph00dz at 10:55 AM on June 23, 2006


No, the server is offsite
posted by finitejest at 11:01 AM on June 23, 2006


totally sounds like a DNS problem


are you running NAT on the server?
is your office LAN tunneled to your server LAN?
what address do you get from your office when you do an nslookup on your server (Windows/Run/cmd.exe, type in 'nslookup MY_SERVER')
what is your office DNS set to.

What happens when you try to hit the domain using the IP address instead of the domain name?
posted by fishfucker at 1:50 PM on June 23, 2006


You're not using hostony.com, are you? (I ask because one of my coworkers had the exact same issue.)

Anyway, if it resolves right on the nameserver front, try running a traceroute to the machine to see where it won't route.
posted by ph00dz at 1:52 PM on June 23, 2006


Actually, we're using ev1servers.net. No NAT, its just a regular webserver used for hosting domains.

here's the results of the nslookup:
C:\Documents and Settings\Artroom>nslookup ndesigns.net
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 65.5.48.8: Timed out
Server: ns2.cl.bellsouth.net
Address: 205.152.16.8

Non-authoritative answer:
Name: ndesigns.net
Address: 66.98.244.29
posted by finitejest at 2:36 PM on June 23, 2006


hmmmmm. It's handing you back the right address ... uhm. I'm guessing the 65.5.48.8 machines is one of yours and it doesn't have rDNS set up for it?

you should probably go with ph00dz recommendation next.
posted by fishfucker at 4:04 PM on June 23, 2006


« Older How to relieve pain from braces   |   freeware pop3 forwarding? Newer »
This thread is closed to new comments.