Modifying hosts file

[m3coolpix]

Working on migrating to new web server. For temporary access to the new server, editing the hosts file (MacOS Monterey) in terminal.

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
22.22.22.22 mywebserver.com
::1 localhost


Saved and exit. Test ping in Terminal works to the new box, see the correct IP address, new hosting company.

However, any browser always go to the old site, say 11.11.11.11 of mywebserver.com (current hosting company) Same for FTP software.

I've tried clearing browser caches/history, rebooting....hosts file never seems to be resolved correctly outside of the terminal UI.

Any ideas? Thanks in advance!

 

[splifingate]

[edit: -ra/-er]

Inter-Server DNS propagation takes time . . . report back in 72h with the same diag, if you will

 

[Bigwaff]

First, make sure you are editing /private/etc/hosts

Second, flush DNS cache -

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

 

[m3coolpix]

First, make sure you are editing /private/etc/hosts

Second, flush DNS cache -

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

It is the /private/etc/hosts file I'm editing. Just quadrillion checked

And have done the sudo killall -HUP mDNSResponder process. Again, it works resolving correctly inside Terminal for the ping both ways. No edit, I get the old server ping address. With edit, I get the new server ping address. Added the sudo dscacheutil -flushcache option just now....same result.

Just really odd that it's working inside terminal as I would expect, but not with any apps or browsers (after clearing cache/history/etc).

And....@splifingate, the hosts file (at least when it's working correctly), over rides DNS for direct connection. The DNS swap over hasn't happened yet.

Here's the hosting company directions:

https://www.knownhost.com/kb/how-can-i-test-my-migrated-website-before-changing-the-dns/

 

[splifingate]

The DNS swap over hasn't happened yet.

Time be time, my Friend

 

[m3coolpix]

Time be time, my Friend

That clock has not and does not start, if the DNS records at the registrar (or servers in my case as they are custom setups) have not been modified.

 

[splifingate]

That clock has not and does not start, if the DNS records at the registrar (or servers in my case as they are custom setups) have not been modified.

Seems you have a lot of time on your hands *shrugs*