Date Confirmation Prior to the go live, your Digital Implementations Manager will request an email from you, stating the specific Date and Time (and timezone) we are to have the site ready to accept traffic.
This email is our permission to complete steps such as removing the site password and modifying the site to use your final site addressing (eg: investor.website.com)
Our preparation steps include updating the menus and links on your Beta site. Links may appear to stop working. This is normal, and is expected! Once the DNS change is complete, the links will begin working again.
CNAME for investors.example.com to point to *Your Q4 websites unique web farm address
And/Or
A Record for example.com to point to IP: 162.159.129.11
*Your Q4 Digital Implementation Manager will provide you with your unique web farm address post kickoff
Below are some additional considerations that will help ensure the transition is smooth:
Domains Please ensure that you have confirmed your final choice for your site with your Implementations Manager well in advance of go-live (eg: investors.domain.com vs ir.domain.com)
If the site will utilize an SSL certificate, please ensure Q4 is made aware of any additional domains early to include in the process. Any additional domains and subdomains will need to be whitelisted by Q4, be included in your SSL certificate and need a DNS CNAME to your Q4 websites unique web farm address.
Timing Q4 will work with you to establish a cutover date and time to go live. Once this date is confirmed, please confirm it in email, confirming the Date, Time and TImezone you will be modifying your DNS. All members of your team and Q4 Implementation manager should be advised. Q4 requires at least 48-72 hours notice to prepare your site for launch.
TTL Propagation of DNS changes usually take less than 30 minutes, but in some cases, it can be longer. For the domains Q4 will be hosting, please request that your team reduce the TTL (Time-To-Live) values, to 300s or as low as possible.
This must be done at least 24 hours in advance, to ensure time for . setting in your DNS configuration, please set it as low as possible ahead of the update. If there is a lead-time required by the team that will be managing the DNS change, please inform Q4 so we can factor this into our deployment plan.
Trailing Dot You may need to include a dot ‘.’ At the end of the webfarm address we provided (subjective to how your domains are administered). Please ensure you review and confirm the Zone Record Entry is correct once you save the changes.
Internal DNS To avoid issues with internal corporate users, please ensure DNS settings for internal servers at are also updated. This is to ensure users accessing the site from within your internal network will be able to see the change as well.
Proxies Q4 strongly recommends avoiding the use of proxies which may process traffic upstream before sending to our webfarms rather than directly routing traffic to them from the client domain(s). This configuration is not natively supported by the platform and will cause issues with monitoring, caching, publishing, etc. Q4 ensures that such proxy setups are not necessary, as we offer multiple layers of best-in-class attack mitigation and security features with all of our products. For more information regarding these, please refer to our security controls documentation, available upon request.