Dyn Status Updates

Scheduled - On Tuesday, May 11, between 19:00 and 20:00 UTC, we will be releasing version 5.2.62 of our Dyn Managed DNS platform to production.

Once complete, changes from this release will be published in our change log along with previous releases.
https://manage.dynect.net/help/changelog.html

No customer impact is expected for this release.

Customers with questions or concerns are encouraged to reach out to our Technical Support team.
May 10, 20:47 UTC

Scheduled - On May 5th, 2021 between 17:00 and 18:00 UTC, we will be updating the Primary DNS infrastructure for the Dyn Managed DNS platform.

During this time, propagation of primary zone updates will be delayed or briefly unavailable. No impact to DNS query resolution for existing records is expected.

Customers with questions or concerns are encouraged to reach out to our Technical Support Team.
May 4, 20:22 UTC

Scheduled - As part of our continued efforts to improve Oracle Cloud Infrastructure and Services, the Oracle Cloud Infrastructure Networking team will be performing planned maintenance on OCI Web Application Firewall (WAF). It is important that you add to the whitelist the newly added subnets listed below:

- 129.148.156.0/22
- 130.35.228.0/22
- 192.29.140.0/22
- 138.1.112.0/20

These IP ranges will expand the existing source ranges for requests originating from the Web Application Firewall (WAF) to your origin. Failure to whitelist these additional subnets at your origin before May 4th, 2021 may result in an impact to any traffic/services routing requests to your origin(s) via the Web Application Firewall service.

Starting May 4th, 2021 all web applications will have their traffic routed through this expanded infrastructure.

How will this affect my service?
There may be an impact on traffic/services from WAF to your origin if the subnets are not whitelisted on your end after May 4th, 2021.

What action do I need to take?
Configure your servers to accept connections from the CIDR ranges listed in the "Securing Your WAF" section of the following document:
https://docs.oracle.com/en-us/iaas/Content/WAF/Concepts/gettingstarted.htm

Customers with questions or concerns are encouraged to reach out to our Support team.

Ref: CN-81099
Apr 19, 16:57 UTC

Scheduled - On May 3rd 2021, between 1700 and 1800 UTC, we will be updating the secondary DNS infrastructure of the Dyn Managed DNS platform.

During this time ingress and egress of secondary zones, secondary egress of primary zones, and creation of primary zones via zone transfer will be delayed or briefly unavailable. No impact to DNS propagation of primary zones or query resolution is expected.

Customers with questions or concerns are encouraged to reach out to our Technical Support team.
May 1, 00:33 UTC

Scheduled - As part of our continued efforts to improve Oracle Cloud Infrastructure and Services, the Oracle Cloud Infrastructure Platform team is performing an expansion on the Web Application Firewall (WAF) service. Due to the nature of the DNS for root domains (also known as apex domains), only DNS 'A' records can be applied. This prevents WAF from assigning your application a new WAF IP address on your behalf.

For maximum scalability and resiliency, applications should avoid using DNS 'A' records and instead use sub-domains exclusively.

How will this affect my service?
There will be an impact on traffic/services that are utilizing WAF IP addresses if new IPs from the list are not being used after May 3rd.

What action do I need to take?
If you are utilizing WAF for root or 'apex' domains by using WAF IP addresses, please make sure to update the 'A' records with one of the new WAF IP addresses below:

US: 147.154.3.128
EU: 147.154.225.212
APAC: 192.29.50.64
AUS: 192.29.152.173

Customers with questions or concerns are encouraged to reach out to our Product Support Team.
Apr 8, 20:14 UTC