Published 2/13/2023
What is Changing?
We are excited to announce that we have migrated our backend services from Microsoft Azure to Amazon Web Services. The change allows us to maintain a higher uptime and redundancy level and provide even better performance. All domains need to have the DNS setting updated to point to the new servers.
LinkTrust will change our SSL and Domain Management to include SSLs for free as a standard service to all clients and domains that are using the new load balancer set-up.
Exact details on this change will be communicated separately.
How Are You Impacted?
All white-labeled (custom) domains need to be updated to point to the new load balancers. Not all LinkTrust clients will need to make modifications. Below is a set of scenarios to which you, as a client, can compare to each domain. Depending on your scenario, you may be contacted to make some modifications.
If you are unsure of what scenario your custom domain(s) fall under, LinkTrust will reach out to you before any DNS updates are made to ensure a smooth transition for your domains.
Scenario 1: No white-labeled/custom domains
All new accounts will come with some default domains for tracking, the affiliate center, and the merchant center. LinkTrust fully manages these domains, and no action is required on your side.
These custom domains will follow a format similar to company.ltroute.com or domain_name.ltroute.com. There are variances in the domain structure and what domain you have. Below is a complete list of domain names that you might have on your account:
- (company).ltroute.com
- (company).lnjmp.com
- (company).affiliate-reporting.com
- (company).merchant-reporting.com
- (company).ltmrkt.com
- (company).linktrustleadgen.com
Scenario 2: LinkTrust Manages the Domain or DNS Settings
If the domain is fully managed, and LinkTrust is the one who purchased the domain and managed the yearly registration for the domain, no action is required on your end. LinkTrust will continue to manage the domain, and the domain will be migrated soon.
Many clients still manage the registration for the domain but have it pointed to our Azure nameservers. If this is the case for your domain, no action is required on your side, and LinkTrust will change the DNS settings.
Scenario 3: LinkTrust does not manage the domain
If you and the nameservers own the domain and are not pointed to our Azure nameservers, you will be contacted to make the change. You will first need to add DNS records for domain ownership verification to set up the SSL; then, you will be given a CNAME for a subdomain or an A record for a root domain to point the domain to the new servers.
LinkTrust will contact you when we are ready to migrate your domain. We will work with you to make sure you have enough time to update the DNS resources in the domain for a smooth transition.
Questions? Please contact support at support@linktrust.com or by live chat Monday through Friday, 8:00 AM - 5:00 PM MST.
FAQs:
Should I expect downtime when my domain is migrated?
No. We will work with you to ensure that the domain is fully set up. You should expect no loss of traffic during the transition of your domain. If you are the domain owner or have control of the DNS settings, LinkTrust will contact you to ensure the SSL is in place before providing the new DNS records to our new Load Blanacers.
Here are some tips to reduce the likelihood of downtime if you are not pointing the domain(s) to our Azure nameservers:
- Lower the Time-To-Live (TTL) to 1-5 minutes for quick changes.
- Update the old record - do not delete it and add a new one unless you change from an A record to a CNAME.
- Make the change during hours when you receive low traffic.
- Do not make changes until we confirm with you that the new SSL has been verified.
What is the timeline for LinkTrust to contact me about changing my domain’s DNS settings?
We plan on reaching out to clients as early as 2/13/2023.
We will migrate domains in waves, with plans to finish by the middle of March.
Have the outbound servers changed as well?
Yes. If you are running a system that requires our outbound IPs to be whitelisted, they will need to be updated to the new IPs:
3.12.121.137
52.14.244.78
The old Azure outbound servers have already been disconnected.