Search Engine: Elastic

Article ID: 128981, created on Jun 21, 2016, last review on Aug 9, 2017

  • Applies to:
  • Operations Automation


Provisioning task has failed with the following output:

Can not create DNS record for ... of type ... There is existing record with id ... and data ...

The error may also appear during any attempt to edit resources of a service template that includes APS 1.2 application resources:

  • adjust resource type limits
  • unprovide resources
  • add resources

The log entries from osscore log:

Aug  3 13:06:56.976 : DBG [UI:12b2f946:1119923:1501758424824 1:3449:a27dbb70 SAAS ]: [ APS::DNSAspect::updateResources] Generating new records
Aug  3 13:06:57.057 : INF [UI:12b2f946:1119923:1501758424824 1:3449:a27dbb70 SAAS ]: [ removeDNSRecords] [APS] Removing DNS record (host : "", data : ""v=spf1 -all"")
Aug  3 13:06:59.188 : INF [UI:12b2f946:1119923:1501758424824 1:3449:a27dbb70 SAAS ]: [ createDNSRecords] [APS] Adding DNS record (host : "", type: "TXT", data : "v=spf1 -all")
Aug  3 13:06:59.468 : DBG [UI:12b2f946:1119923:1501758424824 1:3449:a27dbb70 lib ]: [ void<unnamed>::createDNSRecords] {module_id="APSManager"; code="37"} Can not create DNS record for '' of type TXT. There is existing record with id 109272 and data '"v=spf1 -all"'.
Aug  3 13:06:59.469 : DBG [UI:12b2f946:1119923:1501758424824 1:3449:a27dbb70 SAAS ]: [ APS::DNSAspect::updateResources] <=== EXIT (by exception) [2.545830]


By design, in case of APS 1.2, any change to subscription resources triggers a full reconfiguration of DNS records: APS controller fetches the list of records the subscription APS 1.2 application(s) owns and re-adds them to the system. No check is done if the records currently exist or not. This leads to a possible error, when there are same records added manually under the account, since APS controller changes only system records.


Remove the manually added DNS records from the affected subscription and re-try the operation. Add the records again, if needed.

Please contact Odin Technical Support if the issue cannot be resolved by editing DNS records in CP.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF