ATTENTION: removal of old traveloka.com private DNS records

DEAR PRODUCT DEVELOPMENT TEAMS, TEAM LEADS AND PRODUCT OWNERS. PLEASE READ THIS CAREFULLY AND SHARE WITH OTHERS.

To unblock creation of dedicated AWS accounts and increase agility of the engineering product teams, Site-infra is approaching the last stage of removing the legacy traveloka.com private DNS zone from the shared production account. For more details see project plan and timeline.

Current Status

Stage (I) - stopping use old DNS records is complete. While there are still some records listed as application dependencies, we assume that 11 weeks of time was sufficient for product teams to update their code/configurations with new values, so we consider stage I-A done. Site-Infra has finished re-configuration of MongoDB clusters, thus stage I-B is also done.

Stage (II) - removal of unused old DNS records will be finished next week (August 27-31, 2018). We will start by first removing MongoDB records (see detailed schedule) and then detaching the private zone with all remaining non-MongoDB records. After this, any applications that still relies on old private zone records will start having issues either immediately or after DNS cache of the application/OS has expired. Thus please note: this is your last chance to ensure your production application is not impacted.

Stage (III) - complete removal of old private DNS zone will be executed the week of September 10, 2018.