Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Safari cannot find websites while windows can

Safari says it cannot find wunderground.com - weather and it cannot find Drudgereport.com -- what is up?

Posted on Jul 10, 2014 3:03 PM

Reply
13 replies

Jul 10, 2014 3:54 PM in response to levigirln4runner

Can you run a nslookup (or dig) from MAC OS X Terminal?


dig drudgereport.com


; <<>> DiG 9.8.3-P1 <<>> drudgereport.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12073

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0


;; QUESTION SECTION:

;drudgereport.com. IN A


;; ANSWER SECTION:

drudgereport.com. 544 IN A 98.158.19.137

drudgereport.com. 544 IN A 98.158.27.203


dig wunderground.com


; <<>> DiG 9.8.3-P1 <<>> wunderground.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10950

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0


;; QUESTION SECTION:

;wunderground.com. IN A


;; ANSWER SECTION:

wunderground.com. 184 IN A 38.102.136.104

Jul 10, 2014 4:05 PM in response to levigirln4runner

here is what I got second time

; <<>> DiG 9.8.3-P1 <<>> drudgereport.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 30831

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0


;; QUESTION SECTION:

;drudgereport.com. IN A


;; Query time: 4109 msec

;; SERVER: 10.0.0.1#53(10.0.0.1)

;; WHEN: Thu Jul 10 18:04:29 2014

;; MSG SIZE rcvd: 34

Jul 10, 2014 4:09 PM in response to Loner T

Here is what I received Loner

here is what I got second time

; <<>> DiG 9.8.3-P1 <<>> drudgereport.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 30831

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0


;; QUESTION SECTION:

;drudgereport.com. IN A


;; Query time: 4109 msec

;; SERVER: 10.0.0.1#53(10.0.0.1)

;; WHEN: Thu Jul 10 18:04:29 2014

;; MSG SIZE rcvd: 34

Edit

Jul 10, 2014 4:17 PM in response to levigirln4runner

Try the same for wunderground.com.


If you notice, you are not getting an IP address back in your dig output, so Safari cannot get to the web site by name. Your DNS resolution is not working as expected.


To get to drudgereport.com, in Safari, please try the following...


http://98.158.19.137

http://98.158.27.203


To get to wunderground.com, in Safari, please try the following...


http://38.102.136.104

Jul 10, 2014 5:14 PM in response to levigirln4runner

In your browser, the names you type are translated to addresses by Safari. For these two specific web sites, the DNS server 10.0.0.1#53(10.0.0.1) is unable to find the addresses as indicated by absence of the following section in your output.


;; ANSWER SECTION:

wunderground.com. 184 IN A 38.102.136.104


Is this your Home network or your Work network? Depending on the answer, there are two different solutions.

Jul 10, 2014 6:34 PM in response to levigirln4runner

On the Windows computer, in a command prompt window, please type nslookup wunderground.com

and if you can post the output.


On the MAC, assuming you are connected to your home network via WiFi, under System Preferences -> WiFi -> Advanced -> DNS Tab, click on the left hand '+' sign under the DNS Servers box and enter the following two entries (remove any other entries) and test Safari.


  • 208.67.222.222
  • 208.67.220.220


You can also use 8.8.8.8 (Google DNS) instead of these.

User uploaded file

Jul 10, 2014 7:18 PM in response to levigirln4runner

The current fix is temporary. If your MAC reboots, the problem may come back. All your WiFi Access Points in the house must go to a Router/Gateway which may be your equipment or provided by your Internet Service Provider. The Distributed Name Service (aka DNS) inside your wifi network forwards requests to some external servers (the numbers we put in your MAC DNS Tab). This usually does not require any intervention, but in your case from inside your home network, requests are not being answered. It may be related to your internal network configuration or the ISP router/gateway or the MAC.


Usually the internal network uses DHCP to assign addresses to your devices, which also assigns a DNS server. The 10.0.0.1 is an address in your network. (53 is a port number). When your MAC sends name lookups (like nslookup or dig) it does not get a timely response. Why that happens is what needs to be figured and fixed? The ISP DNS service terminates at their router/gateway. The internal network is managed by you.


Do you have access to your ISP router/gateway? It may help to know who your ISP is to narrow down possible equipment and solutions,

Safari cannot find websites while windows can

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.