Discussions

Eloqua's Move to OCI - Product Notice: POD 6 -> Eloqua Microsite DNS Configured with CNAME/A Records

JodyMooney-Oracle
JodyMooney-Oracle Product Management, EloquaPosts: 349 Employee
edited Apr 29, 2022 6:30AM in Eloqua

UPDATE: As of Feb 24, 2022, all customers should have received their unique IP addresses via email. If you have not yet received yours, or have questions, please contact Oracle Cloud Support. They have a comprehensive list and can provide you with the guidance you require.

INFORMATION FOR POD 6 CUSTOMERS ONLY

In preparation for Eloqua's Move to Oracle Cloud Infrastructure (OCI), and in alignment with recommended best practices, Eloqua customers who have configured their domain name system (DNS) entries by updating a domain’s A record to point to Oracle Eloqua’s IP Address are required to make a configuration change. Failure to update the configuration prior to the posted deadlines will result in microsite errors and will disrupt your Eloqua web traffic.

We have identified customers who are affected by this required change and are reaching out proactively as we move through the Move to OCI for POD 6 customers. If you are unsure, please work with your IT team to confirm if you are impacted.

What’s changing?

In preparation for Eloqua's Move to Oracle Cloud Infrastructure (OCI), and in alignment with recommended best practices, Eloqua customers who have configured their domain name system (DNS) entries by updating a domain’s A record to point to Oracle Eloqua’s IP Address are required to make a configuration change. With the move to OCI, our Public IP address will change, and in general Public IP Addresses may change over time which makes using the A record problematic.

Customers whose branded landing page, application, or tracking domains subdomains (hereafter referred to as “web traffic”) currently use an A record must update their DNS to use a CNAME record instead. The CNAME configuration should be updated as follows:

  • Branded landing page and tracking domains should CNAME to s[siteID].hs.eloqua.com
  • Branded application domains should CNAME to s[siteID].t.en25.com

Note: If your microsite domain is not changed from A record to CNAME, you will be required to update the A record prior to May 1, 2022 to prevent any downtime with your microsite.

  • There will be an overlap of the current IP address for the A record, and the NEW OCI IP addresses. Note: These new IPs are being finalized and we expect to be able to provide them no later than February 24, 2022. More information will be shared once they are approved. At this time you are highly recommended to book time with your IT/ Engineering team so that the change can implemented between February 24 and May 1, 2022.

If you fail to make these changes prior to the May 1, 2022 deadlines, your microsite/landing pages will become inaccessible. For example, landing pages that are collecting form submissions and preferences (subscription management) will be lost and revenue may be directly impacted.


What if my web traffic subdomain is also used as a bounceback? We strongly recommend that you do not use the same subdomain for your web traffic and bounceback. If you are unable to separate the subdomains, you will not be able to use a CNAME and will be asked to update your A record with a new public IP after your Eloqua POD has made the Move to OCI (POD 6 – action needing to be taken between February 24 and May 1, 2022). More information will be provided when the public IP addresses are available.

 

Timeline

For your affected Eloqua microsites, you are asked to update your A record to CNAME configuration no later than by May 1, 2022.

  • If you are unable to do so, you will need to update the IP address your A records point to no later than May 1, 2022.  
  • Note: There will be an overlap between the existing IP addresses and new ones issued for the Move to OCI, and as such you will not have any disruption with your A records between Oct 22, 2021 and May 1, 2022.
  • These new OCI IPs are being finalized and we expect to provide an update with the specific IP address no later than February 24, 2022. More information will be shared once they are approved. At this time, you are highly recommended to book time with your IT/Engineering team so that the change can implemented between February 24 and May 1, 2022.

After May 1, 2022, the existing IPs will be decommissioned, and you must have the new OCI IPs in place.

Next Steps

Customers should reach out to their IT team to:

  1. Discuss these upcoming changes and verify if your Eloqua microsites are affected, and
  2. Reserve time within your IT/Engineering team’s project schedule/sprint cycle to implement the required changes prior to the May 1, 2022 deadline – as they may need more than 3 month's notice in advance.
  3. We recommend that you work with your DNS administrator to lower the TTL ("Time to Live") value of the existing DNS entry to make it easier to test immediately after you make the change. For example, mostly likely the TTL of the DNS entry is set to 24 hours. Ask your DNS administrator to lower TTL to 1 minute. Wait at least 24 hours, then have your DNS administrator make the A/CNAME record update. Since the new 1 minute TTL should already be in effect, you can check your affected domains to confirm that they still function as expected by opening landing pages in preferred browser and verify that the content renders successfully. Once confirmed, it is now safe to you can ask your DNS administrator to increase the TTL back to normal value.

Additional Resources

 

FAQ

Q: Where can I learn more about the changes coming with the move to OCI?

A: You can read more about Eloqua’s Move to the OCI here: https://community.oracle.com/topliners/discussion/4345402/eloquas-move-to-oci-data-centers


Q: When does POD 6 Move to OCI?

A: POD 6 scheduled to move took place on Oct 22nd, 2021. You can find more information here.


Q: How can I make sure my microsites are still working after updating the IP Address?

A: You can check domains to confirm that they still function as expected by opening these in preferred browser and verify content render successfully. Refer FAQ for more details on how to verify different domains.

How to verify Application domain?

Open following URL in browser and verify contents with small dot image render successfully. Replace <application domain> with your valid application domain such as example.com

-- Unsecured domain : http://<application domain>/e/FooterImages/FooterImage1

-- Secured domain: https://<application domain>/e/FooterImages/FooterImage1


How to verify Landing pages?

Login to Eloqua application and capture Landing page URL for domain you want to verify. Open Landing page in any browser and verify that contents render successfully.


 

Group Product Manager, CX - Marketing: Eloqua

Post edited by OIT Integration User on
Tagged:

Comments