Setting up test devices with a DNS override

The following steps allows you to test the Instart configuration without changing public DNS resolution records. This is important for testing traffic resolution without disrupting your end user experience, prior to switching to Instart. 

Get the IP address

Use the dig or nslookup commands from a command prompt with the Instart DNS CNAME to obtain an IP address for testing. You can get this DNS CNAME from Instart customer support, or you may have had it provided to you during your activation.

For example, using nslookup in a Windows command prompt (with the CNAME for as an example):


Non-authoritative answer:

Edit the hosts file on your browser test systems

Next, add the following two lines to the hosts file on each browser test system, using the IP address you obtained above and using the appropriate domain name in place of the example ones below:

#----- <Customer name> -----#

On Windows:

The hosts file is in C:\Windows\System32\drivers\etc

You need to have administrative credentials to edit it.

On Mac:

The hosts file is in /etc

You need to have administrative credentials to edit it.

Browser testing

Clear the browser cache and flush DNS on Windows/Mac and you are ready to test. This will confirm a fresh view based on the local DNS. This has no effect on the public DNS.

To confirm that we are serving the contents for you, you can view the HTTP response header (using the browser tools like Firebug, IE headers, Charles Proxy, or Fiddler) to confirm that objects are being routed through Instart. You should see something like the following in the header:

x-instart-cache-id: 5:6246235656887008991::1493892970


The x-instart-cache-id is only present for cached resources; uncached resources will only have the X-Instart-Request-ID.

When you have finished testing, remember to revert your changes in the test computer's hosts file!