Articles in this section

See more

Unable to create a new domain/subdomain or migrate/rename an existing domain/subdomain: DNS record already exists

Avatar
Kuzma Ivanov
Updated
Follow
Plesk for Windows Plesk for Linux FR:PPM-1981 kb: technical ext: migrator

Applicable to:

  • Plesk for Linux
  • Plesk for Windows

Symptoms

    • When creating a new domain/subdomain/alias, migrating an existing domain/subdomain or activating the mail service for a domain, the operation fails with one of the following errors:

      PLESK_ERROR: DNS records for domain with such name already exist

      PLESK_ERROR: The subdomain with such name already exists

      PLESK_ERROR: This DNS record already exists.

      PLESK_ERROR: Unable to create the subdomain test.example.com. because a DNS record pointing to the host test.example.com. already exists.

      PLESK_ERROR: Unable to set up the domain alias example.net because a DNS record pointing to the host example.net already exists.

      PLESK_ERROR: An error occurred during domain creation: DNS records for a domain with such a name already exist.

      PLESK_ERROR: Plesk API call failed example.com: [Error 1007] DNS records for a domain with such a name already exist.

    • On attempt to apply the changes to DNS template at Tools & Settings > DNS Template > Apply DNS Template Changes, the operation fails with the following error message:

      PLESK_WARN: There were issues syncing DNS zones with the DNS zone template.
      Unable to resolve dns zone owner

    • The following error message appears in /var/log/plesk/panel.log:

      CONFIG_TEXT: ERR [panel] Unable to synchronize DNS zone [6] example.com: Unable to resolve dns zone owner

  • in Windows Error log:
    Unable to find domain or alias 'mydummydomain.com' in database
    at (PSADatabase::getBaseDomainName line 395)
    at Unable to execute console command: '--update'(vconsoleapp::start line 95)
    at Unable to execute command: '"C:\Program Files (x86)\Plesk\/admin/bin/dnsmng" --update "--zone-name=example.com" --without-reverse'(vconsoleapp::run line 117)
    Execute file name: C:\Program Files (x86)\Plesk\admin\bin\dnsmng.exe

Cause

Orphaned DNS records exist in the Plesk database.

Resolution

 

For Plesk on Linux

 

  1. Connect to the Plesk server via SSH.

  2. Create a database dump of the Plesk database (for more information, see this KB article):

    # plesk db dump psa > /root/psa_backup.sql

  3. Access the Plesk database:

    # plesk db

  4. Find dns_zone_id of the domain, which cannot be created, using the following command. Replace example.com with an actual domain name:

    MYSQL_LIN: mysql> select dns_zone_id,host from dns_recs where host like "%example.com%";
    +-------------+---------------------+
    | dns_zone_id | host                |
    +-------------+---------------------+
    | 3           | www.example.com.    |
    | 3           | example.com.        |
    | 3           | ns2.example.com.    |
    | 3           | ns1.example.com.    |
    | 3           | example.com.        |
    | 3           | ftp.example.com.    |
    | 3           | example.com.        |
    | 3           | example.com.        |
    | 3           | _dmarc.example.com. |
    | 3           | example.com.        |
    | 3           | mail.example.com.   |
    | 3           | ipv4.example.com.   |
    +-------------+---------------------+

  5. Using dns_zone_id from the output above, make sure that the domain name is the same:

    Note: In some cases the output may be empty.

    MYSQL_LIN: mysql> select id,name from dns_zone where id=3;
    +----+-------------+
    | id | name        |
    +----+-------------+
    | 3  | example.com |
    +----+-------------+

  6. Delete records from corresponding tables using the ID from the steps above. In case all zones for all domains need to be removed the where id=x can be omitted:

    MYSQL_LIN: mysql> delete from dns_zone where id=3;
    mysql> delete from dns_recs where dns_zone_id=3;
    mysql> delete from dns_refs where zoneId=3;

  7. Exit MySQL:

    MYSQL_LIN: mysql> exit

  8. Create the domain/subdomain/alias in Plesk / Rerun the migration.

 

For Plesk on Windows

 

  1. Connect to the Plesk server via RDP.

  2. Start a command prompt as an Administrator.

  3. Create a database dump of the Plesk database (for more information, see this KB article):

    C:\> plesk db dump psa > C:\psa_backup.sql

  4. Access the Plesk database:

    C:\> plesk db

  5. Run these commands to remove orphaned records:

    MYSQL_WIN: delete from dns_recs where dns_zone_id in (select id from dns_zone where id not in (select dns_zone_id from domains) and id not in (select dns_zone_id from domain_aliases));

    MYSQL_WIN: delete from dns_zone where id not in (select dns_zone_id from domains) and id not in (select dns_zone_id from domain_aliases);

  6. Exit MySQL:

    MYSQL_WIN: mysql> exit

  7. Create the domain/subdomain/alias in Plesk / Rerun the migration.

 

 

Comments

3 comments

Sort by Date Votes
  • Avatar
    cit dev

    How to solve probleme if no ssh access?

    0
    Comment actions Permalink
  • Avatar
    Alisa Kasyanova

    @cit dev
    SSH is mandatory in this case because Plesk database cannot be accessed via GUI. Please contact your server provider in order to solve it.

    1
    Comment actions Permalink
  • Avatar
    cit dev

    Ok thanks!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles