Mobile app version of vmapp.org
Login or Join
Karen161

: Access site not working for the owner I made a website, and it works for everyone except for the site owner, who cannot access the site. He gets a "server could not be found" error. I went

@Karen161

Posted in: #Apache #Dns #Domains

I made a website, and it works for everyone except for the site owner, who cannot access the site. He gets a "server could not be found" error. I went to his house and the issue occurs for all of his devices (PC, laptop, iPhone using WiFi) when I turn WiFi off on the iPhone it works.

So I thought it was a problem on his router, so I reset his router to default factory settings but it still does not work. I have flushed his DNS cache and his browser cache, but nothing seems to help. He cannot even PING the server using the domain name. However, when he uses the IP address, he can see the site fine.

I looked in cPanel for an blocked IP addresses but cannot see anything. What could be stopping just him from accessing the site via domain name and not the IP address?

Site details are: PHP, osCommerce, and it is hosted by site5 on my reseller account.

10.05% popularity Vote Up Vote Down


Login to follow query

More posts by @Karen161

5 Comments

Sorted by latest first Latest Oldest Best

 

@Vandalay111

Every time I've run into this, its been due to caching. Normally the client has visited an older (non-functional) version of the site, and this has been cached in their browser. This is enhanced if it is an older browser. or especially if they are behind some sort of proxy. Having a reverse proxy on the site, such as CloudFlare, would also cause this caching.

Point it, they most likely have an old copy cached. Either it is a browser cache, a proxy cache, or even at some point along the way, a DNS cache. Figure out how to clear/reset that, and you should be good to go!

Based on the issues across multiple devices, it is apparent that it is almost certainly a DNS caching issue, with an old request from before the site was set up being cached somewhere along the way. Try using an alternate DNS provider (8.8.8.8 and 8.8.4.4 for Google), and flushing their DNS cache (sudo dscacheutil -flushcache on a Mac).

10% popularity Vote Up Vote Down


 

@Cofer257

Configure the dns with the dns hosts of your site5 account.

10% popularity Vote Up Vote Down


 

@Bryan171

You should try taking one of your devices to the client's home (it could be a laptop or just a smartphone) and connect it via wifi.


If the web works, we can assume the problem is related to your client's computers configuration. I could be that he has the same antivirus installed on all the devices.
If you can't connect to the web, it must be a ISP-related problem. It might be a ban or just an issue of DNS caching.

10% popularity Vote Up Vote Down


 

@Holmes151

Is your host site an apache host site? Are you running an .htaccess file? And possibly mised up your allow from and deny from statements.

10% popularity Vote Up Vote Down


 

@Steve110

If domain name just registered better will be wait for 72h

Anyway you can run traceroute on PC and find where is the problem.

tracert domain.com


If you don't understand output clean first two octets with xxx.xxx.1.1 and post it in you question.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme