Testing RedShield using static hostnames

Prior to migrating traffic onto RedShield Cloud, customers are advised to perform application functional testing to ensure that no user impact occurs following migration. 

Recommendations for testing: 

- Basic testing should include browsing the application as various user types, logging in, and testing page loading and basic functions. 

- More thorough or specialised testing may be appropriate for non-browser applications such as APIs, or any applications with Advanced Shielding applied. Your RedShield Engineer can advise on this during setup.

- Testing traffic assists with the RedShield policy tuning process, and should comprise normal user traffic only. Please do not include security testing such as penetration testing techniques or scanning tools, except by arrangement with RedShield engineers.


Testing may be performed as follows: 


Step 1: Determine which hostname you would like to test, eg, and ensure you have the correct CNAME as issued by RedShield such as 

Determine the IP address which RedShield has assigned to your application, using a command similar to the following: 

OSX: host

Windows: nslookup


Step 2. Set a static entry into your workstation's hosts file


sudo vi /etc/hosts

Add a host entry similar to the following:


Save the file using :w! 



Open Notepad as Administrator (depending on your version of Windows and your logged-in user's level of system privilege, procedure may vary - please see Microsoft documentation). 

Open and edit the file C:\Windows\System32\drivers\etc\hosts.

Add a host entry similar to the following:

Save the file. 


Step 3. Test the application using a browser or other client testing tools, which should now use the configured static host entry instead of querying DNS. You may have issues with browsers or other clients caching a previously queried DNS value; in which case you may need to close all open tabs and windows in the browser and reopen before trying again. Opening a different browser may be useful as an alternative method.  


Step 4: If no issues are detected within the application, revert the changes applied in the previous steps and proceed to migration. 


Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request