8

I have not had a similar issue in Windows (10) and nothing I've searched on docs seems to indicate why, if this does not work, that that is the case

  • I open up terminal and edit /etc/hosts (which I've done many times on a PC and a few years back on an OSX too)
  • Just for grins if that doesn't work I type in sudo killall -HUP mDNSResponder
  • Then for more grins I reboot

This has absolutely no effect. Can anyone point me to why? Thanks.

UPDATE: The embarrassing fact of the matter is that the lines I entered in /etc/hosts were in reverse, i.e. domain first, as:

mydomain.com  192.168.33.10    #wrong
192.168.33.10    mydomain.com  #what it should have been

The accepted answer, however, is well-written and appreciated.

miken32
  • 42,008
  • 16
  • 111
  • 154
Oliver Williams
  • 5,966
  • 7
  • 36
  • 78
  • It works just fine. So you did something wrong, or you expected wrong. There is not enough information in your question to guess which. – Calle Dybedahl Feb 15 '17 at 20:46

3 Answers3

30

I've seen two common problems with using /etc/hosts on macOS (/OS X):

  • Incorrect formatting: each entry in the /etc/hosts file must be an IP address followed by a space or tab, followed by the name, then a linefeed at the end of the line. Try printing the hosts file with cat -vet /etc/hosts to make normally invisible characters visible. Each line should look like one of these:

    127.0.0.1^Iwww.example.com$
127.0.0.1 www.example.com$

    (The "^I" is a tab, and the "$" is the linefeed at the end of the line.) It's also ok if the entry has multiple names listed (also separated by spaces or tabs).

    If you see a "^M" (carriage return) just before the "$", you have DOS/Windows formatted text and you need to remove the carriage return(s).

  • Incorrect testing: Don't use the command-line tools dig, host, and nslookup, since they all test DNS directly and therefore bypass the /etc/hosts file. Browsers sometimes cache things, which can give misleading results. The "right" way to test the system's name resolution system is with the dscacheutil command:

    dscacheutil -q host -a name www.example.com

    ...but since that's annoyingly verbose, I tend to just use ping, and see what address it says it's going to test.

Gordon Davisson
  • 118,432
  • 16
  • 123
  • 151
  • this is in the "I'm almost too embarrassed to admit I did this department". I put the domain name first and the IP address second. I will leave this question and your excellent answer here to a) keep me humble and b) in hopes it helps someone. If the community feels it should be deleted I'll gladly defer. – Oliver Williams Feb 16 '17 at 11:17
  • Thank you! It was exactly my several days problem! – Alekzander Jan 08 '20 at 19:25
3

I came across this thread to try and solve the same issue on macOS Catalina and was not successful. This is because macOS Catalina has another thing going; it will only make changes in the hosts file effective if you change them as the root user (this is not done with the sudo command) !!

By default there is not a root user on your system so here's a link with a step by step guide to do so: https://support.apple.com/en-us/HT204012

then I was able to:

su
nano /etc/hosts

for more information: https://discussions.apple.com/thread/250805304

Dharman
  • 30,962
  • 25
  • 85
  • 135
joronimo
  • 563
  • 5
  • 8
0

Below steps worked for me

  1. flushing DNS sudo killall -HUP mDNSResponder (or kill DNS in activity monitor and let it reload)

2.Changing read-write permissions of /etc/host file should be -rw-r--r-- .Use commands $ sudo chmod g+r /etc/hosts and $ sudo chmod o+r /etc/hosts

  1. Adding entry u want to add in host file with ipxxx.xx.xx.com

  2. moved these 2 lines in the end 255.255.255.255 broadcasthost ::1 localhost Administrators-MacBook-Pro.local

  3. Step 1 again

simerbhatti
  • 87
  • 2