Safari "Can't find server" when using WiFi at hot spots?

This is a DNS issue.

Often, domain name servers are identified in the configuration files of the router or gateway you are using. If they are not, and are not identified on your iPhone, this is precisely the sort of response you will see when querying a domain by canonical name—as virtually everyone does—rather than numeric internet protocol address.

Check the iPhone's IP address when you receive that error... it sounds as though the iPhone is not receiving a valid IP address. Go to Settings > Wi Fi and click on the blue circle with a white arrow in it next to the name of the network in question. If it begins 169.x.x.x it is not a valid IP address. Try resetting the iPhone's network settings by going to Settings > General > Reset > Reset Network Settings.

CG

Hi! I have a similar problem. The IP address begins with 169.x.x.x.x. I have tried resetting the network settings but again it takes the same IP address. How do I change and get the valid IP address so that I can connect to the Internet using WiFi.

Thanks & regards

Aditya

For this issue, you should also try powercycling your access point if you are able to do so. Basically, turn the router off, wait about 10 seconds, turn it back on, and then test the iPhone again.

CG

Try removing the DNS numbers that the router has sent and use: 208.67.222.222

I've had this problem also.

@Michael; And the solution to this DNS issue is?

It all depends upon your configuration.

You should first determine in a case like this if your iPhone or other device has been assigned a valid DHCP address.

If you see a value like 169.x.x.x, you have not been assigned a valid DHCP address. This may occur for many reasons, most often because the DHCP server component of your router is not issuing them, or your device is not commmunicating with it. Valid DHCP addresses are generally in the ranges of…

• class A: 10.0.0.1 through 10.255.255.255
• class B: 172.16.0.1. through 172.31.255.255 and seldom used, and
• class C: 192.168.0.1 through 192.168.255.255

If you have a valid DHCP address, then the issue is likely that your router is not properly configured, in that it does not have valid DNS server addresses stored in its configuration files.

Generally, a router or gateway requires that you configure its assigned address, a valid subnet mask, and primary and secondary DNS servers. While you can use any valid DNS address for primary, secondary, tertiary and subsequent server entries, by convention, most technicians set the pair assigned by the internet service provider for your service area. In Eugene OR, for example, Comcast DNS addresses are set to…

• primary: 68.87.69.146 and
• secondary: 68.87.85.98

Check to see that your router or gateway configuration contains such information, as the result of being issued a valid DHCP address but not being able to identify a DNS server leads to the sort of issue outlined by the original poster.

You can easily determine if this is the case by querying a known site by its numeric address, rather than by its canonical name. If one takes you to the site but the other fails to do so, then you have the DNS issue I referred to.