Article ID: 121939, created on Jun 8, 2014, last review on Nov 4, 2016

  • Applies to:
  • H-Sphere 3.6.3
  • Operations Automation 6.0
  • Plesk Automation 11.5

Symptoms

Plesk Automation does not allow to use underscore "_" in CNAME records.

Cause

The functionality which you expect from the Plesk Automation - ability to use underscore "_" in CNAME records - can be considered as a feature request.

The feature request number #PPA-1230 regarding the matter was created.

Please use provided ID to track maintanance in PA release notes.

Subscribe to our knowledge base - each product update comes with corresponding KB article:

https://kb.odin.com/rss/index.html

Workaround

  1. Add required record manually in domain configuration file on DNS server:

    /var/named/run-root/var/<domain.tld.>
    

    where domain.tld name of required domain

  2. Restart DNS server:

    # service named restart
    

Note: as soon as the zone is modified the zone file will be regenerated by system and all manual changes will be lost. In order to permanently add such record in the zone contact Odin Technical Support as such action requires manual intervention into PA database.

Search Words

problem with creation cname record

We are unable to add a CNAME record containing an underscore.

dsadasdsa

Amazon AWS

Cant add _ to cname plesk automation

Allow to add a CNAME record in DNS with a leading underscore ("_") for DKIM. When adding in the current version, we got an error.

_domainkey

cname issue

add dns record cname

CNAME record

DKIM

PPA CNAME office 365

add cname record

cname underscore

rror: Domain names must contain Latin characters, digits, hyphens and dots as separators and must start and end with a letter or a digit

dns records with special character

Using underscore symbol "_" in CNAME records

Incorrect or empty field value(s). Please retype info in the highlighted fields.

plesk dns underscore

underscore

CNAME with underscore _

character "_"

Error: Domain names must contain Latin characters, digits, hyphens and dots as separators and must start and end with a letter or a digit.

33a70544d00d562bbc5b17762c4ed2b3 e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065 f213b9fa8759d57bee5d547445806fe7 6311ae17c1ee52b36e68aaf4ad066387 6b908665c0d1eca5bdd0141a32fd712a 2e39a5e5b1423cc126cf735bac076008 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF