Apple Event: May 7th at 7 am PT

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

Cannot resolve hostname

We've got a WSS3 site hosted on our intranet, internal only. We have one specific iMac on 10.8 (our company VP's machine) which cannot resolve the hostname in Safari or Firefox. Chrome can do it, as can dig, ping, network utility, etc. The DNS cache record has the correct IP. Nothing in hosts. We've restarted the MDNS Responder service, ran dscacheutil -flushcache, cleared local browser caches, run ccleaner, restarted, etc, nothing seems to be working. We just get a cannot connect to server message in the browser. I'm stuck on this, and I'm far from being a Mac expert, I could use some suggestions (other than an OS reinstall, which is a last resort).

iMac, OS X Mountain Lion (10.8.4)

Posted on Jul 26, 2013 11:54 AM

Reply
17 replies

Jul 26, 2013 1:21 PM in response to Linc Davis

Thanks for the reply. The IP of the WSS3 server is 192.168.10.109, you can see our Primary and Secondary domain controllers here (secondary is the first lookup server at this office due to being onsite).


Lookup:


Lookup has started…


Trying "rremployeedashboard.com"

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

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


;; QUESTION SECTION:

;rremployeedashboard.com. IN ANY


;; ANSWER SECTION:

rremployeedashboard.com. 3600 IN A 192.168.10.109

rremployeedashboard.com. 3600 IN NS rrsdc.runroom.lcl.

rremployeedashboard.com. 3600 IN NS rrpdc.runroom.lcl.

rremployeedashboard.com. 3600 IN SOA rrpdc.runroom.lcl. hostmaster.runroom.lcl. 5 900 600 86400 3600


;; ADDITIONAL SECTION:

rrsdc.runroom.lcl. 3600 IN A 192.168.250.24

rrpdc.runroom.lcl. 3600 IN A 192.168.10.25





Received 187 bytes from 192.168.10.25#53 in 25 ms


Ping:


Ping has started…


PING rremployeedashboard.com (192.168.10.109): 56 data bytes

64 bytes from 192.168.10.109: icmp_seq=0 ttl=124 time=7.823 ms

64 bytes from 192.168.10.109: icmp_seq=1 ttl=124 time=7.575 ms

64 bytes from 192.168.10.109: icmp_seq=2 ttl=124 time=7.737 ms

64 bytes from 192.168.10.109: icmp_seq=3 ttl=124 time=9.298 ms


--- rremployeedashboard.com ping statistics ---

4 packets transmitted, 4 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 7.575/8.108/9.298/0.693 ms

Jul 26, 2013 5:00 PM in response to RRIT

That doesn't indicate that the name can't be resolved. It indicates that the web server is refusing connections. Try this in a shell:

curl -I http://rremployeedashboard.com

You should almost instantly get several lines of output, the first of which begins with something like this:

HTTP/1.1


If there's no output within ten seconds, consider that a failure.

Jul 29, 2013 8:07 AM in response to Linc Davis

I will try this when I can (VP is back in office so my access will be limited), however, I realized I forgot to mention on the original post that I can access the site when I enter the IP directly into the browser. It's only when I use the dns name that I cannot connect, which is why I believed it was a name resolution issue.

Aug 2, 2013 9:13 AM in response to RRIT

Step 1


From the Safari menu bar, select

Safari Preferences... Privacy Remove All Website Data


and confirm. Test.


Step 2


From the Safari menu bar, select

Safari Preferences Extensions

Turn all extensions OFF and test. If the problem is resolved, turn extensions back ON and then disable them one or a few at a time until you find the culprit.


If you wish, you may be able to salvage the malfunctioning extension by uninstalling and reinstalling it. Its settings will revert to their defaults. If the extension still causes a problem, remove it permanently or refer to its developer for support.

Aug 12, 2013 11:16 AM in response to RRIT

Please read this whole message before doing anything.

This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.


These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.


Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.


Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.


Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.


Launch the Terminal application in any of the following ways:


☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)


☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.


☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.


When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.


Step 1


Triple-click the line of text below on this page to select it:

kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -f -a TextEdit

Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.

Step 2


Repeat with this line:

{ sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; echo; sudo defaults read com.apple.loginwindow LoginHook; echo; sudo crontab -l; } 2> /dev/null | open -f -a TextEdit

This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.


Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.


Step 3

{ launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; echo; crontab -l 2> /dev/null; } | open -f -a TextEdit

Step 4

ls -A /e*/{cr,la,mach}* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -f -a TextEdit

Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.


Step 5

osascript -e 'tell application "System Events" to get name of every login item' | open -f -a TextEdit

Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output.


You can then quit Terminal.

Cannot resolve hostname

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