• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk 12.5MU3 Creating CNAME throwing error

bsass

Basic Pleskian
I'm trying to create a CNAME record that I used to do all the time in 9.5.4 and then last week we upgraded to 12.5. When trying to create a CNAME record of bob.domain.com that points to page.domain.com it throw an error of:

Incorrect combination of DNS records is present in the DNS zone

That's using both the CLI and also the web interface.

I was reading about CNAME causing loops and not being allow but I don't think this is the case, here is how the record flow is and works still but can't add anything new:

bob.domain.com points to CNAME pages.domain.com which points to CNAME pages.3rdpartyhosting.com

Thanks for the help!
 
Hi bsass,

the restrictions for DNS - records are based on standards, which are clarified as for example at: RFC 2181 => https://tools.ietf.org/html/rfc2181
The general standards are defined at: RFC 1034 and RFC 1035 and the additional memo RFC 2181

Quoted from RFC 2181:
10.1. CNAME resource records

The DNS CNAME ("canonical name") record exists to provide the
canonical name associated with an alias name. There may be only one
such canonical name for any one alias. That name should generally be
a name that exists elsewhere in the DNS, though there are some rare
applications for aliases with the accompanying canonical name
undefined in the DNS. An alias name (label of a CNAME record) may,
if DNSSEC is in use, have SIG, NXT, and KEY RRs, but may have no
other data. That is, for any label in the DNS (any domain name)
exactly one of the following is true:
RFC 2181 Clarifications to the DNS Specification July 1997


+ one CNAME record exists, optionally accompanied by SIG, NXT, and
KEY RRs,
+ one or more records exist, none being CNAME records,
+ the name exists, but has no associated RRs of any type,
+ the name does not exist at all.

10.1.1. CNAME terminology

It has been traditional to refer to the label of a CNAME record as "a
CNAME". This is unfortunate, as "CNAME" is an abbreviation of
"canonical name", and the label of a CNAME record is most certainly
not a canonical name. It is, however, an entrenched usage. Care
must therefore be taken to be very clear whether the label, or the
value (the canonical name) of a CNAME resource record is intended.
In this document, the label of a CNAME resource record will always be
referred to as an alias.

If you need further assistance, please include the correct fully qualified domain name ( FQDN ) for investigations, please.
 
UFHH01. I respect every one of your replies, that I read daily, I have told you want I can. I can't give you the real responses. I can tell you that everything is my first post it right and that I under how the DNS system works.

Thanks
 
Back
Top