Search Engine: Elastic

Article ID: 123637, created on Nov 22, 2014, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4


Customer is trying to create DNS record of the CNAME type . He is specifying an underscore in record name. OA returns an error:

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


Prior to OA version 6.0.3, underscores in CNAME record names are not supported. However, 'Canonical name' field still cannot handle underscores. Feature Request #POA-100983 is filled to implement missing functionality.


Please, consider updating your OSA installation to the latest version.


NOTE: This CNAME record can't be managed from CCP.

  1. Login into the name servers and backup the domain "domain.tld" zone file.
  2. Then add the requested CNAME record to the zone file.

    [root@ns1 ~]# grep 'smtpapi._domainkey.domain.tld' /var/named/run-root/var/domain.tld.
    smtpapi._domainkey.domain.tld.            CNAME   dkim.domain.tld.
  3. Reload the zone file.

    [root@ns1 ~]# named-checkzone domain.tld /var/named/run-root/var/domain.tld.
    /var/named/run-root/var/domain.tld.:1: no TTL specified; using SOA MINTTL instead
    zone domain.tld/IN: loaded serial 51772
    [root@ns1 ~]# rndc reload domain.tld
    zone reload queued
    [root@ns1 ~]# rndc reload domain.tld
    zone reload up-to-date
  4. Then it can resolve the host "smtpapi._domainkey.domain.tld" within the name servers.

    [root@ns1 ~]# dig -t CNAME smtpapi._domainkey.domain.tld @ns1.provider.tld +short
    [root@ns2 ~]# dig -t CNAME smtpapi._domainkey.domain.tld @ns2.provider.tld +short
    [root@ns3 ~]# dig -t CNAME smtpapi._domainkey.domain.tld @ns3.provider.tld +short

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF