Forwarded to devs Plesk issues an incorrect warning that a CNAME doesn't resolve

[mr-wolf]

TITLE:

Plesk issues an incorrect warning that a CNAME doesn't resolve​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk 17.8 / CentOS​

PROBLEM DESCRIPTION:

After adding a CNAME-record for a TXT-record and updating the DNS-settings Plesk will test the existence of an A-record for these CNAMEs and when these do not exist it will incorrectly warn me that it doesn't resolve.

CNAMEs are not only used for A-records, but also for TXT-records.​

STEPS TO REPRODUCE:

Add a CNAME that only resolves to a TXT-record and then update the settings​

ACTUAL RESULT:

A warning is given that the CNAME does NOT resolve




# host -t TXT s1._domainkey.myclient.nl
s1._domainkey.myclient.nl is an alias for s1.domainkey.u990967.wl218.sendgrid.net.
s1.domainkey.u990967.wl218.sendgrid.net descriptive text "k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDnuLubEIyEzWHRHM9k3o5hg3K4FP4lsi/Nhe+n8GU1ovi/6P8ur7f8rCXAxedUh+1sM1zO5cCA5dEzHit2qSHO2ojHD/HZbLvKCTJ0LZB0php+0hTqmvhZ5CbNPSPt8AlcicAWQai9ot/DFgmwMISSCjOnc3rRsdxJQurrMPV32QIDAQAB"

# host -t A s1.domainkey.u990967.wl218.sendgrid.net.
s1.domainkey.u990967.wl218.sendgrid.net has no A record

# host -t TXT s1.domainkey.u990967.wl218.sendgrid.net.
s1.domainkey.u990967.wl218.sendgrid.net descriptive text "k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDnuLubEIyEzWHRHM9k3o5hg3K4FP4lsi/Nhe+n8GU1ovi/6P8ur7f8rCXAxedUh+1sM1zO5cCA5dEzHit2qSHO2ojHD/HZbLvKCTJ0LZB0php+0hTqmvhZ5CbNPSPt8AlcicAWQai9ot/DFgmwMISSCjOnc3rRsdxJQurrMPV32QIDAQAB"


​

EXPECTED RESULT:

It should also test if the target resolves as a TXT-record, not only an A-record.
If that resolves it should keep quiet.
Only issue a warning if neither an A-record or a TXT-record resolves (maybe more types, but this is a realistic situation).
​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

I confirm it is Plesk bug, issue PPPM-7993 was created.
Thank you for report.

 

[websavers]

We’re seeing a *lot* more CNAME to TXT records because of DKIM rollout for Google services. This means more people than ever are being confused by this warning. Would be nice to see this addressed.