Changing your hosts file to test your domain during migration

  Print
Sometimes you may need to test your domain while in the middle of a migration project. The easiest way to do this is by changing your HOSTS file and manually setting the IP and domain.

Windows

  1. Open your Start Menu and search for Notepad.
  2. Right click on Notepad and select Run as Administrator - this step is important otherwise you will not be able to edit the HOSTS file.
  3. Go to File > Open and navigate to C:\Windows\System32\drivers\etc and select to view ALL FILES and then select HOSTS.
    IVieEtR.png
  4. On a empty line, type in your account or server IP address and then a space and then your domain name. For an example, see the green highlighted section below.

    AAqSjiw.png
  5. Now go to File > Save (or press CTRL+S). If you receive an access denied error, you need to re-open Notepad as an Administrator in Step 2.
  6. At this point, you should use a different web browser or clear your web browser's temporary files. At this point, you can try to access your domain. We recommend making a small change so that way you are sure which version of the site you're on. Or, if you haven't uploaded any files yet or if our staff hasn't begun the migration, you won't see anything except an empty directory which would indicate that the HOSTS file is working.

Mac OS X

  1. Launch Terminal, found in /Applications/Utilities/ or launched through Spotlight
  2. Type the following command at the prompt:
sudo nano /private/etc/hosts Enter the administrator password when requested, you will not see it typed on screen as usual with the command line
oF94Ltz.png Once the hosts file is loaded within nano, use the arrow keys to navigate to the bottom of the hosts file to make your modifications
f1RhkMa.png When finished, hit Control+O followed by ENTER/RETURN to save changes to /private/etc/hosts, then hit Control+X to exit out of nano Quit out of Terminal when finished You can verify your hosts modifications immediately with ping, Safari, or any other network app. Changes take effect immediately though some adjustments may need to be accompanied by a DNS flush which can be done with the following command in OS X 10.9:

dscacheutil -flushcache;sudo killall -HUP mDNSResponder
When flushing DNS cache with that command you will need to enter the admin password.

Did you find this article useful?   0 out of 0 people found this article useful.

Related Articles


  • Comments

Add Comment

Replying to  

Self-Hosted Help Desk Software by SupportPal.

Login

 
Forgot password?
Register now

Language