Article ID: 115249, created on Dec 4, 2012, last review on May 11, 2014

  • Applies to:
  • Operations Automation 5.4

Symptoms

In POA, Office 365 tasks fail with this error message:

Can not create DNS record for <FQDN> of type TXT. There is existing record.

See the example below:

Task name       APS application 'Microsoft Office 365', id 180, instance 4068 -> service 'customer', instance 7506: executing configuration script
Last execution output   Can not create DNS record for '<FQDN>' of type TXT. There is existing record with id <ID> and data '"v=spf1 include:outlook.com ~all"'._

Cause

The srv_records.php/srv_records.py script described in the Office 365 Known Issue: SRV Records for Lync Online Are Not Created Automatically KB article was customized in the following way:

  • This customized script creates DNS TXT records when new subscriptions are provisioned. These DNS TXT records are created through the POA Public API.

  • The created DNS TXT records are marked as "MANUAL."

After that, the subsequent APS configuration tasks fail because the Office 365 APS application cannot create/update DNS TXT records. The application cannot create/update DNS TXT records because the APS service controller does not allow the creation of a DNS record if there are already DNS records of the same type that were created manually or by another APS application.

Resolution

For Microsoft Office 365 Application 4.4 and higher:

  1. Revert the srv_records.py script to the "canonical" form. Set the Text of SPF DNS records global setting of the appropriate Office 365 Application Resource Type to the proper value (the v=spf1 include:outlook.com ~all value is default).

  2. Extract the content of the updateDNSRecords.zip file. Run the updateDNSRecords.py script. This script is configured in the same way as is described in this KB article: #112991. The script updates the DNS TXT records created by the customized srv_records.py script as if they were created by the Office 365 application.

Note: An individual subscription can be fixed as follows: remove the "MANUAL" DNS TXT record for the domain mentioned in task's execution output; restart the failed task.

For Microsoft Office 365 Application 4.3 and lower:

  1. Revert the srv_records.php script to the "canonical" form. Set the Text of SPF DNS records global setting of the appropriate Office 365 Application Resource Type to the proper value (the v=spf1 include:outlook.com ~all value is default).

  2. Run the attached script, updateDNSRecords.php. This script is configured in the same way as is described in this KB article: #112991. The script updates the DNS TXT records created by the customized srv_records.php script as if they were created by the Office 365 application.

Note: An individual subscription can be fixed as follows: remove the "MANUAL" DNS TXT record for the domain mentioned in task's execution output; restart the failed task.

Search Words

Office365

Can not create DNS record for

TXT

Can not create DNS record for

Attachments

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF