Article ID: 113908, created on May 17, 2012, last review on Jun 1, 2015

  • Applies to:
  • Plesk 12.0 for Windows
  • Plesk 10.4 for Windows


MS DNS is used to serve sites’ DNS requests. When trying to add an NS record, create a subscription, or change the server hostname, the following error is received in Plesk:

<span><font>Error: Set default component failed: defpackagemng failed: Execute dnsmng.exe UPDATE \* failed with error code 1: Unknown error 0x80131501 (COM Error 80131501, Description: Generic failure ) at resetSecondaries ZoneName = …</font></span>


The issue may be caused by MS DNS behavior. It automatically creates basic NS records based on the server's hostname.

When a similar DNS record is created manually, or from a DNS template during subscription creation, the above conflict occurs. The same will happen if server’s hostname is changed to a value, that already exists among NS records on the server.


Our development team is working on improving the above behavior. You may subscribe to Panel Products Updates mailing list if you wish to receive notifications about the latest product updates, new version announcements, promotions, and more for Plesk, and Plesk Billing.


Two workarounds are possible:

  1. Switch DNS provider from MS DNS to another one (BIND, for example).

  2. Avoid situations, when some NS record matches server’s hostname.

Search Words

Execute dnsmng.exe UPDATE \* failed with error code 1

dns hostname fqdn

Unknown error 0x80131501

Error: Set default component failed

c796c01d6951fa24ed54c7f1111667c6 a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 56797cefb1efc9130f7c48a7d1db0f0c ed7be2b984f9c27de1d2dc349dc19c6d a766cea0c28e23e978fa78ef81918ab8 ff5a00b8ead2e480367b019417a04207

Email subscription for changes to this article
Save as PDF